Flaky tests
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Random test failures due to HTTP errors. The following are a couple of examples:
- https://community-tc.services.mozilla.com/tasks/f3ohmJxOR_-djDot25FHew/runs/0/logs/public/logs/live_backing.log#L292
- https://community-tc.services.mozilla.com/tasks/CyAjj5WMTjuvS16neqt1Rw/runs/0/logs/public/logs/live_backing.log#L241
Using mocks can be a solution. I'm not sure if we could reuse mozilla/libmozdata/blob/master/tests/auto_mock.py.
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 reproducing the HTTP-related failures and inspect the linked live_backing.log excerpts to identify which tests make the requests. Review tests/auto_mock.py in mozilla/libmozdata as a possible reference for isolating those requests; done means the affected tests run deterministically without the reported HTTP failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100