Parallel tests exit with wrong status #20027
Labels
bug
Indicates an unexpected problem or unintended behavior
priority
This should be addressed urgently
testsystem
The unit testing framework and Test stdlib
Milestone
Over at least the last few weeks, when tests get run in parallel (as on CI) and there's a failure, the overall execution isn't exiting with a nonzero status like it should be. This has been hiding several issues. For example,
The abstractarray failure here isn't the important part (it was fixed by #20018), this issue is about that fact that tests "passed" with the failure present.
The text was updated successfully, but these errors were encountered: