Fix ASSERT failure and re-enable setnumcapabilities001
authorSimon Marlow <marlowsd@gmail.com>
Wed, 11 May 2016 14:38:25 +0000 (15:38 +0100)
committerSimon Marlow <marlowsd@gmail.com>
Wed, 11 May 2016 16:05:10 +0000 (17:05 +0100)
commitcfc5df43a7789832a2789e517d8270650cc31b7f
tree782040443734324cfaa38ae0bae7b884bd144286
parent3edbd091341ab0ab60862ba18d3107f34c7fc876
Fix ASSERT failure and re-enable setnumcapabilities001

The assertion failure was fairly benign, I think, but this fixes it.
I've been running the test repeatedly for the last 30 mins and it hasn't
triggered.

There are other problems exposed by this test (see #12038), but I've
worked around those in the test itself for now.

I also copied the relevant bits of the parallel library here so that we
don't need parallel for the test to run.
rts/Schedule.c
testsuite/tests/concurrent/should_run/all.T
testsuite/tests/concurrent/should_run/setnumcapabilities001.hs