Commit 5262d70e authored by Simon Marlow's avatar Simon Marlow
Browse files

Skip conc036 entirely (see comments)

parent 95cb0a1d
...@@ -152,14 +152,21 @@ test('conc034', compose(only_compiler_types(['ghc']), ...@@ -152,14 +152,21 @@ test('conc034', compose(only_compiler_types(['ghc']),
test('conc035', only_compiler_types(['ghc']), compile_and_run, ['']) test('conc035', only_compiler_types(['ghc']), compile_and_run, [''])
# Omit for GHCi: firstly GHCi doesn't have unsafe FFI calls, and secondly # conc036: now skipped entirely. This test attempts to check that
# the main thread cannot receive the deadlock exception because it can be # unsafe foreign calls block other threads, but doing that reliably is
# woken up by ^C. # probably impossible. The last straw was when it started failing on
# Omit for threaded2: this test is really bogus and fails to do anything # Windows around 7.4.x.
# sensible for more than one CPU. #
test('conc036', compose(skip_if_fast, # OLD comments about hacks we tried to make it work:
compose(omit_ways(['ghci','threaded2']), # Omit for GHCi: firstly GHCi doesn't have unsafe FFI calls, and secondly
only_compiler_types(['ghc']))), compile_and_run, ['']) # the main thread cannot receive the deadlock exception because it can be
# woken up by ^C.
# Omit for threaded2: this test is really bogus and fails to do anything
# sensible for more than one CPU.
#
test('conc036', skip, compile_and_run, [''])
# Interrupting foreign calls only makes sense if we are threaded # Interrupting foreign calls only makes sense if we are threaded
test('foreignInterruptible', composes([skip_if_fast, test('foreignInterruptible', composes([skip_if_fast,
only_threaded_ways, only_threaded_ways,
......
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