Update tested GraalPy version in CI #4867
Conversation
|
Hi @davidhewitt, I'm trying to update the GraalPy version used in CI, as you requested in #4802. Can you please give me the CI full label to run it? Should I keep the old version in the matrix as well? Or should I change the minimal supported version in the docs? |
|
What is your upstream support policy for making graalpy versions end of life? We should probably not drop support before you do. |
|
GraalPy's EOL is either the EOL of the corresponding Graal version (the .0 versions are LTS) or the CPython version it implements, whichever comes first. So, 24.0 should EOL some time in 2026. I was just concerned about your CI usage, since the graalpy jobs tend to be more demanding. I'll keep both versions then. |
msimacek
force-pushed
the
msimacek/graalpy-24.1
branch
4 times, most recently
from
55af1eb to
a06dcf9
Compare
msimacek
force-pushed
the
msimacek/graalpy-24.1
branch
from
a06dcf9 to
cefc8a4
Compare
msimacek
force-pushed
the
msimacek/graalpy-24.1
branch
from
7ca4921 to
17b78a7
Compare
|
@davidhewitt, this should be ready. Unfortunately there is one test that fails because of a bug on our side. It is fixed already on our master, so it should work again in the next release. I skipped it on 24.1. Sorry about that, we should add pyo3 tests to our CI to prevent that from happening again. |
No description provided.