Skip to content

foreignInterruptible is fragile

Recently I have observed numerous failures of foreignInterruptible in the ghci way:

=====> foreignInterruptible(ghci) 558 of 7594 [0, 0, 0]
cd "concurrent/should_run/foreignInterruptible.run" && "/builds/Phyx/ghc/inplace/bin/ghc-stage2" foreignInterruptible.hs -dcore-lint -dstg-lint -dcmm-lint -no-user-package-db -rtsopts -with-rtsopts=--io-manager=native -fno-warn-missed-specialisations -fshow-warning-groups -fdiagnostics-color=never -fno-diagnostics-show-caret -Werror=compat -dno-debug-output  --interactive -v0 -ignore-dot-ghci -fno-ghci-history +RTS -I0.1 -RTS < foreignInterruptible.genscript
Wrong exit code for foreignInterruptible(ghci) (expected 0 , actual 1 )
Stdout ( foreignInterruptible ):
newThread started
fail
Stderr ( foreignInterruptible ):
foreignInterruptible: still waiting
*** unexpected failure for foreignInterruptible(ghci)

I'm not sure what changed recently as I swear this wasn't a common failure a few months ago.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information