OpenAstronomy / OpenAstronomy/github-actions-workflows
How to handle already existing wheels for daily dev builds
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 27
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 1
Description
Over at Astropy we are building nightly wheels - sometimes there are no changes from one day to the next so the anaconda upload fails with:
Creating release "5.2.dev275+g8ef58665f"
[303](https://github.com/astropy/astropy/runs/7442665386?check_suite_focus=true#step:6:304)
Uploading file "astropy/astropy/5.2.dev275+g8ef58665f/astropy-5.2.dev275+g8ef58665f-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl"
[304](https://github.com/astropy/astropy/runs/7442665386?check_suite_focus=true#step:6:305)
Distribution already exists. Please use the -i/--interactive or --force or --skip options or `anaconda remove astropy/astropy/5.2.dev275+g8ef58665f/astropy-5.2.dev275+g8ef58665f-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl
What would be the best approach here?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Astropy GitHub Actions run and trace the workflow step that uploads nightly wheels to Anaconda. Compare the repeated-build failure with the workflow configuration and determine how unchanged daily builds should be handled; done means a duplicate wheel no longer causes the workflow to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- anaconda, github-actions, python
- Domain
- build-system, ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100