-
Notifications
You must be signed in to change notification settings - Fork 46
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
CI failing for 32-bit #587
Comments
I'm not sure if GAP didn't stop supporting 32 bit builds, maybe I'm misremembering. If 32 bit is no longer needed, then we can just drop this CI job. Alternatively, it'd probably suffice to increase the version of ubuntu used in the CI job, which might resolve the issue too. Writing in a hurry, maybe completely wrong... |
Looks like it fails on all GAP branches: master, stable-4.12 and stable-4.11. So I guess it's not that GAP has dropped it. https://github.com/digraphs/Digraphs/actions/runs/5012528703/jobs/8984579183 |
Ubuntu 23.04 (Lunar Lobster) released a month ago, and our tests are pointed at |
Nope, looks like the tests are using Ubuntu jammy, so no change there. The issue is on installation:
I think this comes from setup-gap/action.yml: https://github.com/gap-actions/setup-gap/blob/44a8ae68e262dd0d22b84ef146460741b4c06c70/action.yml#L37C1-L66 Some funny business with dependencies. |
Raised at gap-actions/setup-gap#45 |
I'll just mention to remind us that Digraphs has some 32-bit specific code, so if and when we stop testing on 32-bit, I'd recommend dropping our 32-bit support and ripping out that code. |
Good point @wilfwilson, a super satisfying deletion of code will follow :) |
My reading of @fingolfin's last comment on: is that 32-bit continuous integration for GAP is not currently feasible (or at least not worth the effort). I tend to agree, I don't think this is the same as dropping support for 32-bit though, I'd suggest we retain 32-bit support until either:
At that point we can drop support for 32-bit, and remove any relevant special code. What do @mtorpey and @wilfwilson say? |
I agree! We can leave our code in there in case it's useful to someone. However, to resolve this issue: should we drop 32-bit from our test suite? |
Thanks @mtorpey: yes, let's drop 32-bit from the test suite. I'll make a new issue about 32-bit support. |
This is superseded by #602. |
As shown at:
https://github.com/digraphs/Digraphs/actions/runs/4806182761/jobs/8963120783
To start with I thought this was my PR, but when I rerun the main branch it's doing it too. Probably a bug in the tests or in GAP?
The text was updated successfully, but these errors were encountered: