mozilla-releng / mozilla-releng/redo
don't show tracebacks unless all attempts are exhausted
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 101
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
In automation at Mozilla, we do a lot of heuristic log parsing to find exceptions and highlight them. One of the scenarios we've been running into a lot lately is where we have a job that uses redo, it prints some tracebacks, a subsequent attempt succeeds, but then the job fails for an unrelated reason (eg: a timeout is some non-retried thing). This ends up with the traceback that we successfully retried for getting highlighted, and confusion ensues.
We should stop printing tracebacks at less verbose log levels unless we've exhausted all the attempts.
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
The issue names no files or tests. Start by locating redo's retry and traceback-logging entry points, then reproduce a retry that later succeeds and a final unrelated failure; done means tracebacks are withheld at lower verbosity until all attempts are exhausted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100