We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is very odd - ci is now failing when the arm vms try to install gsutil - complaining that it requires python < 3.12
What is odd is that nothing has changed on our side, and there have been no new pip packages for gsutil
gsutil always had the python version set but for whatever reason pip wasnt enforcing it so the install worked fine
kinda frustrating also as it would require so little effort on gsutil side to resolve this (pending prs including one of mine)
not sure how to workaround this issue rn
The text was updated successfully, but these errors were encountered:
seems its not the installing that broke - its the pre-installed github gsutil - actions/runner-images#11089
trying to think how best to resolve
Sorry, something went wrong.
gsutil
github/ci: Workaround failing gsutil issue (#37480)
6a4608f
workaround for #37479 Signed-off-by: Ryan Northey <[email protected]>
we have a reasonable workaround for this - problem has been acknowledged here actions/runner-images#11089
keeping this open - hopefully we can remove the workaround once upstream is fixed
No branches or pull requests
This is very odd - ci is now failing when the arm vms try to install gsutil - complaining that it requires python < 3.12
What is odd is that nothing has changed on our side, and there have been no new pip packages for gsutil
gsutil always had the python version set but for whatever reason pip wasnt enforcing it so the install worked fine
kinda frustrating also as it would require so little effort on gsutil side to resolve this (pending prs including one of mine)
not sure how to workaround this issue rn
The text was updated successfully, but these errors were encountered: