Improve the way to handle new wpt tests
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
#5790 was done to address #5763, but it is too slow in our workers for some reason, so I did 462d916c52c2551051747f70720f0ad31cc59887.
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 reading #5790 and #5763, then compare the worker-related behavior introduced by commit 462d916c52c2551051747f70720f0ad31cc59887. Identify where new WPT tests are handled and measure the worker slowdown; done means the handling is improved without reproducing the reported performance problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100