You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though there are some failing tests on Windows, the CI doesn't actually fail the job, and considers the job as successful. This was only caught due to the CI also failing on a MacOS job, which was caught successfully.
To Reproduce
Run the Windows CI on a commit which is known to not work with Windows
Observe the log mentioning failed tests
Observe the CI marking the job as successful
Expected behavior
If the Windows tests fail, then the job should reflect that by failing.
Something like this should be a simple fix. In Linux you can set a flag in a script so the whole script fails if any part of it exits with a code. I assume the same can be applied to windows as well.
Describe the bug
Even though there are some failing tests on Windows, the CI doesn't actually fail the job, and considers the job as successful. This was only caught due to the CI also failing on a MacOS job, which was caught successfully.
To Reproduce
Expected behavior
If the Windows tests fail, then the job should reflect that by failing.
Screenshots
N.A.
Platform
Additional context
Notify maintainers
@brynblack
The text was updated successfully, but these errors were encountered: