lincc-frameworks / lincc-frameworks/python-project-template
Smoke test failure sends one message per python version
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 85
- Forks
- 16
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 1
Description
e.g. https://github.com/astronomy-commons/hipscat-cloudtests/actions/runs/8015681836
The action failed for python 3.9 and 3.10, and was cancelled for 3.11. We received two alerts, but they each had the same action/run URL, so it looked like a totally duplicated message.
Would it be possible to have the notification step happen ... outside the python matrix scope? and send an alert if the run fails, not just for each job that fails?
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 GitHub Actions run and inspect the smoke-test workflow's notification step and Python matrix. Confirm how failures currently produce separate job alerts, then adjust the workflow so one alert represents a failed run rather than each failed matrix job; verify the behavior with a matrix run that has multiple failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100