8000 CI: cygwin job is timing out at over 6 hours · Issue #25708 · numpy/numpy · GitHub
[go: up one dir, main page]
Skip to content

CI: cygwin job is timing out at over 6 hours #25708

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and 8000 privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
mattip opened this issue Jan 27, 2024 · 5 comments · Fixed by #25716
Closed

CI: cygwin job is timing out at over 6 hours #25708

mattip opened this issue Jan 27, 2024 · 5 comments · Fixed by #25716

Comments

@mattip
Copy link
Member
mattip commented Jan 27, 2024

The builds https://github.com/numpy/numpy/actions/workflows/cygwin.yml have been timing out for two days. There is a warning about node 20 and the cleanup-path warning, which should be solved by egor-tensin/cleanup-path#2. I don't think that is the problem. Comparing the versions of the packages installed by cygwin between a good and bad run, I see they updated cpython 3.9.16 -> 3.9.18. More likely, but why? Is there a way to pin the python version so we could test that hypothesis? Does anyone see anything else off?
@seberg
Copy link
Member
seberg commented Jan 28, 2024 •
edited
Loading

Ping @DWesl, since it's the Cygwin CI.

@EliahKagan
Copy link
Contributor
EliahKagan commented Jan 29, 2024 •
edited
Loading

This strongly resembles a Cygwin CI timeout on the GitPython repository, described in detail (with some updates in comments) and worked around in gitpython-developers/GitPython#1814. This likewise coincided with the Cygwin python39 package going from version 3.9.16-1 to 3.9.18-1, and pinning that Cygwin package to 3.9.16-1 was sufficient to get things working again.

Is there a way to pin the python version

Cygwin's installer supports specifying package versions, but I was not able to get cygwin/cygwin-install-action to do so. Pinning does work when egor-tensin/setup-cygwin is used. Switching to that action and specifying python39=3.9.16-1 as a package was effective. (I did verify that the action wasn't itself the cause, both by switching the action without pinning as a test, and also by reproducing both the bug and the workaround in Cygwin on a local Windows 10 machine.)

I suspect an analogous change may address the problem here, too.

@EliahKagan EliahKagan mentioned this issue Jan 29, 2024
Merged
@mattip
Copy link
Member Author
mattip commented Jan 29, 2024

Looking through that issue, it seems turning off progress bars in pip may also solve the stall

@mattip mattip mentioned this issue Jan 29, 2024
Closed
@EliahKagan
Copy link
Contributor

For GitPython, turning off progress bars was not sufficient, because another stall occurred while running the tests, in a test that had not been having any problems on Cygwin before.

At least superficially it looks like such a problem happened for NumPy in #25714 as well, though I don't want to assume that, since I see that an alternative explanation (of an actual new bug) has not been ruled out.

@seberg
Copy link
Member
seberg commented Jan 29, 2024

Just hypothesizing, but is there maybe any way to change the shell settings which could affect things, so that the tools will print/draw things differently?
(I.e. maybe it draws like an interactive shell, but it could be set to behave more like a non-interactive one?)

@mattip mattip mentioned this issue Jan 29, 2024
Merged
@charris charris mentioned this issue Jan 29, 2024
Merged
@radarhere radarhere mentioned this issue Jan 30, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@seberg @mattip @EliahKagan
0