-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parallel tests exit with wrong status #20027
Comments
Now that I know what to test for (see discussion in #20210, throwing a BoundsError that has a custom array type in one of its fields that isn't defined on node 1 is a good test case for this), it bisected to 8982605. I'm glad @kshyatt put in the work to make the version of that PR that we wound up merging bisect-clean. |
@tkelman care to open an issue for #20027 (comment) ? Else I'll do it later. |
It sounds as though you may have more ideas on alternatives we could try than I do. |
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: