-
Notifications
You must be signed in to change notification settings - Fork 27
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
Update test target to current Ubuntu #161
Conversation
Co-authored-by: Ondrej Baranovič <nulano@nulano.eu>
Not quite related question - when I run this branch in my own fork, it fails, saying that it is "Unable to find image 'githubactions/ubuntu-22.04-jammy-amd64:main' locally" (whereas main passes). Any ideas why that might be? |
Co-authored-by: Andrew Murray <3112309+radarhere@users.noreply.github.com>
There's a race condition between this image and the test image -- if we're not on main and there isn't a version of it pushed to dockerhub. Because of the branch and username, we're specifically using the test version that's built in this (or your) pr. It might get better on subsequent runs if it's actually pushing to dockerhub, or it won't. |
Should this target Python 3.11 by default? |
No, because Jammy doesn't. |
guess I'm backing up the CI queue today. |
This should help: #162 |
I don't know where that screenshot comes from, but I really don't think that all of the jobs ran 8 times - I expect it was only one of them that had 8 attempts. Our test suite has some intermittent failures, but the main culprit is |
Fix test docker image selection
No description provided.