-
Notifications
You must be signed in to change notification settings - Fork 3.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
[Python][CI] Tests on windows are running very slow #35078
Comments
The first slow crossbow build seems to be 3 days ago: https://github.com/ursacomputing/crossbow/actions/runs/4649634532/jobs/8228109815 |
"raw logs" url seems expired, or just I didn't have authority to visit it? |
Is it a timeout? It's pretty consistent on |
Here's a more recent slow build: https://github.com/ursacomputing/crossbow/actions/runs/4676300747/jobs/8282436089 I usually go to Zulip to find nightly test status: https://ursalabs.zulipchat.com/#narrow/stream/181017-nightlies/topic/report/near/348751506 |
Comparing the last fast and first slow crossbow build, the only external change in the python test environment was an update of pytest from 7.2.2 to 7.3.0, and that might actually be the culprit: pytest-dev/pytest#10896 |
Sorry, wasn't aware that the raw logs urls expire so quickly. Updated the top post with linking to the normal github actions pages, where you can manually click on "View raw logs" |
The new Pytest release fixes the issue. Appveyor is now passing and the wheel tests for Windows are back to ~10 minutes instead of 2hours :). I am closing the issue. |
Appveyor is currently timing out (eg https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/46764558), and also the nightly crossbow wheel tests show very slow tests (eg wheel-windows-cp310-amd64 latest logs).
Going back a bit in time, the same crossbow build from April 1 was fast: logs (tests take about 5 minutes)
The text was updated successfully, but these errors were encountered: