Commit 1053d725 authored by Simon Marlow's avatar Simon Marlow
Browse files

omit conc016(threaded2), it gives nondeterministic results

parent 78dd7f5c
......@@ -88,7 +88,7 @@ test('conc013', only_compiler_types(['ghc']), compile_and_run, [''])
test('conc014', only_compiler_types(['ghc']), compile_and_run, [''])
test('conc015', only_compiler_types(['ghc']), compile_and_run, [''])
test('conc015a', only_compiler_types(['ghc']), compile_and_run, [''])
test('conc016', [ expect_fail_for(['threaded2']), # see comment in conc016.hs
test('conc016', [ omit_ways(['threaded2']), # see comment in conc016.hs
only_compiler_types(['ghc']) ], compile_and_run, [''])
test('conc017', only_compiler_types(['ghc']), compile_and_run, [''])
test('conc017a', only_compiler_types(['ghc']), compile_and_run, [''])
......
......@@ -4,12 +4,13 @@ import Control.Exception
-- check that we can still kill a thread that is blocked on
-- delivering an exception to us.
-- NB. this test is delicate since 6.14, because throwTo is now always
-- interruptible, so the main thread's killThread can be legitimately
-- interrupted by the child thread's killThread, rather than the other
-- way around. This happens because the child thread is running on
-- another processor, so the main thread's throwTo is blocked waiting
-- for a response, and while waiting it is interruptible.
-- NB. this test is non-deterministic in the threaded2 way since 6.14,
-- because throwTo is now always interruptible, so the main thread's
-- killThread can be legitimately interrupted by the child thread's
-- killThread, rather than the other way around. This happens because
-- the child thread is running on another processor, so the main
-- thread's throwTo is blocked waiting for a response, and while
-- waiting it is interruptible.
main = do
main_thread <- myThreadId
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment