-
Notifications
You must be signed in to change notification settings - Fork 288
Update GraalPy to 24.2.2 and remove some Windows workarounds. #2501
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
Conversation
I see some failures (including Windows). |
3c1a3c3
to
9e9332a
Compare
Not having any GraalPy tests at all in PRs is a bit of problem. |
It might just be a networking problem, though, |
21301f6
to
53af2a5
Compare
53af2a5
to
59d91e6
Compare
I copy-pasted the error instead so I could read it (2,000 lines all in one line). Looks like a Java out of memory error. Windows error
|
Thank you, I'm looking into it on a branch on my fork so I don't spam the main CI |
54b607e
to
e47a39e
Compare
I had to keep the workaround. We have another bug on Windows which in this case leads to graalpy recursively spawning new pip processes until the machine runs out of memory. |
This can wait until after the bot and manylinux have picked up the new GraalPy 24.2.2 release, I just wanted to test already that we can remove the workarounds.