-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Intermittent CI failures related to unpacking packages #14079
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
Comments
Tries to fix python#14079.
I think the problem is that "pyright: Run test cases" uses |
Maybe we should be pinning the uv version we install in the setup-uv action to the same version we have in requirements-tests.txt |
That's what I was thinking, although ideally we'd automate that or teach renovate to sync it. |
There's some mentions of bzip2 support in the last two versions of uv. Which is what the CI fails on. Likely related. In any case I agree we should use a consistent version from our pinned dependencies. I wonder if setup-uv can/could automatically pickup the version from dependency groups like the ruff action can. |
For as long as we're using a requirements file, I've opened astral-sh/setup-uv#411. |
(And of course #14082 is a workaround for now.) |
Uh oh!
There was an error while loading. Please reload this page.
We get intermittent failures in CI during the "pyright: Run test cases" step. The failure is always consistent between all three platform this test runs on, and also look consistent within a PR, but the packages it affects are different between PRs. The affected packages have no new releases.
Example from https://github.com/python/typeshed/actions/runs/15062531917/job/42340224286?pr=14078
The errors started yesterday and yesterday a new uv version was released, but we pinned uv to an old version, which also gets installed.
The text was updated successfully, but these errors were encountered: