stack test
seems to non-deterministically fail when executing a test suite for a multi-project repository with parallelism enabled (e.g. stack build -j8 --test
) with the following errors:
/tmp/stack-7235c340cf08101f/test-ghc-env: openBinaryFile: resource busy (file is locked)
/tmp/stack-7235c340cf08101f/test-ghc-env: openBinaryFile: resource busy (file is locked)
/tmp/stack-7235c340cf08101f/test-ghc-env: openBinaryFile: resource busy (file is locked)
/tmp/stack-7235c340cf08101f/test-ghc-env: openBinaryFile: resource busy (file is locked)
/tmp/stack-7235c340cf08101f/test-ghc-env: openBinaryFile: resource busy (file is locked)
/tmp/stack-7235c340cf08101f/test-ghc-env: openBinaryFile: resource busy (file is locked)
I haven't been able to pin down a reliable reproduction, however if I were to guess I'd say it's got something to do with the testGhcEnvRelFile
, possible either colliding with an existing on in this call:
...or bubbling up from Cabal
or ghc
somehow?
Unable to reliably reproduce.
Expectedstack build -j8 --test
should successfully execute all tests in a multi-project repository.
stack build -j8 --test
fails non-deterministically with an error message about busy resources (locked files).
$ stack --version
Version 2.1.3, Git revision 0fa51b9925decd937e4a993ad90cb686f88fa282 (7739 commits) x86_64 hpack-0.31.2
Method of installation
cabal-install
RikvanToor, ulidtko, ludat, vmchale, kfigiela and 1 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4