-
Notifications
You must be signed in to change notification settings - Fork 113
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
Fix CI run on ubuntu-latest-py3.12
#547
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #547 +/- ##
=======================================
- Coverage 98.9% 98.8% -0.2%
=======================================
Files 44 44
Lines 4819 4819
=======================================
- Hits 4770 4765 -5
- Misses 49 54 +5 |
I am not sure why this should be different suddenly for one particular job, but one thing to consider is that our
In the subsequent step: ixmp/.github/workflows/pytest.yaml Lines 119 to 133 in c49a115
It's possible that the overall PYTHONPATH is not making it through this call stack, and thus while A second thing to look into is that the install of reticulate appears to be failing. I don't believe this should cause the other error, but it's a possibility:
|
It's not about |
It's not specifically about |
It may help to try something like |
Indeed: |
GitHub rolled back their shift from Ubuntu 22.04 to 24.04 for |
At the moment, this PR mainly runs the CI checks to debug the mysterious error message observed even after multiple re-runs and cache deletions on
ubuntu-latest-py3.12
:This error is not flaky and does not seem to originate from outdated cached tool versions (at least after removing the
ubuntu-latest-R-4.4.1
cache, the error persisted). It might be related toubuntu-latest
slowly changing to24.04
over the course of this month, but the...-py3.11
test uses the exact same runner image and workflow file without problems.How to review
Required: describe specific things that reviewer(s) must do, in order to ensure that the PR achieves its goal.
If no review is required, write “No review: …” and describe why.
PR checklist