-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
test_time failure in CI logs #25875
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
Comments
Yeah...it seems to fail on and off. |
@gfyoung can you reproduce locally by chance? Tried a few times on macOS with no luck curious if you fared any better |
Of course not. Why would flaky CI make our lives easy? 😂 |
But actually, though, unless we can figure something out now, I think it's best skipping this test (for now) so that we can merge other PR's and return to this before the |
Hmm not sure about skipping the whole thing. I think we could at least salvage everything up until the xlim change and maybe skip everything thereafter for the time being. Could also be explicit about the data to use rather than relying on random |
That's fair.
Possibly, could try that and see what happens. |
Looks like this test is no longer xfailed (and possibly the CI has recovered?) We can reopen if we see it again |
The following failure has shown up a couple times in CI today. Haven't looked in detail but assume it to be an unreliable test.
https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=9836&view=logs&jobId=a69e7846-138e-5465-0656-921e8964615b&taskId=56da51de-fd5a-5466-5244-b5f65d252624&lineStart=42&lineEnd=95&colStart=1&colEnd=64
The text was updated successfully, but these errors were encountered: