Skip to content

threadstatus-9333 fails nondeterministically in ghci way

--- concurrent/should_run/threadstatus-9333.run/threadstatus-9333.stdout.normalised	2019-04-08 01:57:09.409837989 +0000
+++ concurrent/should_run/threadstatus-9333.run/threadstatus-9333.run.stdout.normalised	2019-04-08 01:57:09.409837989 +0000
@@ -3,7 +3,7 @@
 p: emptying full MVar (expect child to be blocked on it)
 p: child is ThreadBlocked BlockedOnMVar
 p: from MVar: full
-p: reading empty MVar
 c: filling empty MVar (expect parent to be blocked)
-c: parent is ThreadBlocked BlockedOnMVar
+p: reading empty MVar
+c: parent is ThreadRunning
 p: from MVar: filled empty var
Actual stdout output differs from expected:
diff -uw "concurrent/should_run/threadstatus-9333.run/threadstatus-9333.stdout.normalised" "concurrent/should_run/threadstatus-9333.run/threadstatus-9333.run.stdout.normalised"
*** unexpected failure for threadstatus-9333(ghci)
Edited by Ben Gamari
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information