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
The following tests in mypyc runtime tests with py39-macos spuriously failed during PR #14934 , even though I did not touch any code related to them:
testIncrementalCompilation1_separate
testIncrementalCompilation4_separate
I added two empty dummy commits to get the pipeline to succeed. The following three commits have no code changes, but for the first two some of the tests fail:
Yeah, the macOS mypyc runtime tests have been flaky for some time now. We have some hypotheses about what might be going on, but as far as I know this still bit of a mystery.
I wasn't aware we had hypotheses! The only thing I confirmed was that it doesn't seem to be related to any code change in mypy, something changed out from underneath us
Fixes#16420
Although this is not 100% clear yet, but after 20 runs on a Mac I have
it no longer fails (without this patch it failed 20% of times). Btw,
contrary to the comment, _my_ Linux Mint (which is an Ubuntu derivative)
works perfectly (i.e. test passed 20 times even after I removed the
`sleep()`). So it is not really Mac vs Linux issue.
Bug Report
The following tests in
mypyc runtime tests with py39-macos
spuriously failed during PR #14934 , even though I did not touch any code related to them:I added two empty dummy commits to get the pipeline to succeed. The following three commits have no code changes, but for the first two some of the tests fail:
To Reproduce
Trigger a CI pipeline run without code changes.
Expected Behavior
The test runs are consistent.
Actual Behavior
Tests spuriously fail. See links to the log files above.
Your Environment
This happened in the CI runs of !PR #14934.
The text was updated successfully, but these errors were encountered: