Skip to content
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

sdist not being uploaded along with the wheels. #167

Closed
WilliamJamieson opened this issue Nov 10, 2023 · 7 comments · Fixed by #169
Closed

sdist not being uploaded along with the wheels. #167

WilliamJamieson opened this issue Nov 10, 2023 · 7 comments · Fixed by #169

Comments

@WilliamJamieson
Copy link
Contributor

This is related to astropy/astropy#15597.

Background

The astropy 6.0rc1 release was triggered, which triggered the building and uploading of the astropy 6.0rc1 wheels to PyPi, see https://github.com/astropy/astropy/actions/runs/6817064464/job/18540287448. The issue is that the source distribution was not uploaded to PyPi along side all the pre-built wheels.

It looks like the Run actions/upload-artifact@v3 step was successfully triggered by all of the wheel builds, see for example https://github.com/astropy/astropy/actions/runs/6817064464/job/18539760549. However, for the source distribution Run actions/upload-artifact@v3 was not triggered, see https://github.com/astropy/astropy/actions/runs/6817064464/job/18539753723.

As far as I can tell, the source distribution upload would only be blocked by:

if: |
needs.targets.outputs.upload_to_pypi == 'true' || inputs.upload_to_anaconda

This appears to be identical to the wheel upload blocker:

if: |
needs.targets.outputs.upload_to_pypi == 'true' || inputs.upload_to_anaconda

Yet the former was blocked while the latter was not. Diving into the logs we see that for both the source and wheel builds the inputs both clearly have upload_to_pypi: true meaning that in both cases the upload should have occurred, see

So I do not understand why one uploads while the other does not. There are no failures in any of the steps proceeding the failure.

@WilliamJamieson
Copy link
Contributor Author

Tagging @ConorMacBride and @Cadair for assistance.

@astrofrog
Copy link
Contributor

I've been investigating this but I also don't understand what is going on. Will keep trying, but in the meantime I think it should be safe to upload a locally built sdist.

@WilliamJamieson
Copy link
Contributor Author

WilliamJamieson commented Nov 16, 2023

The stcal package experienced the same issue (source distribution did not get uploaded to PyPi) today when it made a release. See the log: https://github.com/spacetelescope/stcal/actions/runs/6881432549/job/18717759512

@astrofrog
Copy link
Contributor

Ok I'll try and investigate some more

@astrofrog
Copy link
Contributor

Mystery solved: #169

@astrofrog
Copy link
Contributor

@WilliamJamieson - I've tagged a new release of the workflows so things should work properly next time. Let me know if not!

@WilliamJamieson
Copy link
Contributor Author

I can confirm that this indeed fixed the issue. stcal successfully uploaded everything via the run of: https://github.com/spacetelescope/stcal/actions/runs/6892869688/job/18751126499
see: https://pypi.org/project/stcal/1.5.1/#files for PyPi confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants