-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
raise BadZipFile("Bad magic number for central directory") #215
Comments
It's something in twine that we call to make this upload. Download the dist artifact and inspect it locally. Possibly, file an issue with twine. |
@henryiii is it possible that cibw produces broken wheels? |
I think there might be a bug with actions/download-artifact@v4, I've seen corrupted files from it in nox, too, in wntrblm/nox#772. I think it might be happening there because some of the files have the same file names when you merge.
There are a lot of repeated wheels with same file names if you have |
As a first step, I'd reduce that list of platforms to |
As @henryiii recommended, I reduced down to FYI so I break |
Don’t build with multiple image variations and see what happens. I’m pretty sure merge-multiple corrupts data if there are matching filenames. The version of the image you use doesn’t affect the wheels you produce. |
@henryiii |
I have a similar workflow and it seems to be randomly crashing with the very same error trace, when I download all particular artifacts locally and validate it all is fine:
and this is log from the download:
also rerun the failed job crashes with same issue... |
@Borda its recommended to also validate the metadata earlier in your workflows. In jobs that run in PRs, not just when you publish. This way, you won't be getting last-minute problems. Run As for why local check might be different, not sure. Maybe the versions of twine and CPython are different 🤷♂️. FWIW, now that we switched to pre-cached containers, you should be able to grab the exact one running in the CI and attempt reproducing there. |
Github Actions:
And I tried
- uses: pypa/gh-action-pypi-publish@release/v1.8
, same problem.Interesting thing is that:
if I trigger the os system separately, like below:
os: [ubuntu-latest, ubuntu-20.04]
os: [windows-latest, windows-2019]
os: [macos-latest, macos-11, macos-13]
these three times passed separately.
What happened? Please help.
The text was updated successfully, but these errors were encountered: