-
-
Notifications
You must be signed in to change notification settings - Fork 547
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
GH Actions: WSL workflow fails with failed syscalls #31088
Comments
comment:1
Tobias, when you have a chance, could you try to fix up the WSL workflow please? It's been failing consistently for months now |
comment:2
Sorry, I don't have time for this in the foreseeable future. |
comment:3
Thanks for letting us know, and thanks for all your work in the past months. |
comment:6
It now fails during the installation of flint
Seems to be a version mismatch between flint and bits. |
comment:7
Looks to me like a failed system call when accessing this header file. Is this appearing in more than one run? |
comment:8
Yes, flint fails since 9.4.beta6 see https://github.com/sagemath/sage/actions/workflows/ci-wsl.yml |
comment:9
Is this using WSL 1 or 2? Should we test both? |
comment:10
WSL 1 is the only supported version (WSL 2 would require a self-hosted runner). |
This comment has been minimized.
This comment has been minimized.
comment:12
bump to 9.6 |
This comment has been minimized.
This comment has been minimized.
comment:14
This ticket needs some care so that we can update our instructions for WSL to something that actually works. |
Also reported in https://groups.google.com/g/sage-devel/c/jE6qf0MqriQ/m/cdsEC8SkAgAJ
To fix this, we should probably follow the guidance added in #32714, putting as much of the build in the Linux filesystem.
CC: @tobiasdiez
Component: porting
Issue created by migration from https://trac.sagemath.org/ticket/31088
The text was updated successfully, but these errors were encountered: