Deprecation warning CI jobs are broken
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 40
- Avg merge
- 21h 24m
- Merged PRs (30d)
- 8
Description
It seems to be capturing exceptions that have nothing to do with Deprecations, or else otherwise not providing enough context to be useful.
https://github.com/pulp/pulp_container/actions/runs/29838236577/job/88666507996?pr=2419
https://github.com/pulp/pulp_rpm/actions/runs/29767210275/job/88443743080?pr=4467
Contributor guide
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 two linked GitHub Actions job runs for the deprecation warning checks and compare which exceptions they capture. Trace the CI job configuration and its warning-handling entry point, then verify that unrelated exceptions include useful context while deprecation warnings remain handled by the job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100