OpenAstronomy / OpenAstronomy/github-actions-workflows
binary upload job is uploading all artefacts regardless if that run created them.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 27
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 1
Description
We have two action runs to compile wheels, one for a range of platforms and one for aarch64.
If you see https://github.com/sunpy/sunpy/actions/runs/9915099064 for an example.
The upload step for the non-aarch64 run also tries to upload the aarch64 wheel which feels like it shouldn't be doing?
Is this expected behaviour?
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 by inspecting the reusable workflow used by the two wheel-building runs and compare its upload step with the example run at https://github.com/sunpy/sunpy/actions/runs/9915099064. Determine whether each run should upload only artifacts it created; done means unrelated architecture wheels are no longer selected by the upload step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100