V8 sync bot: Check why tests moved out of staging were re-synced
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
Some tests were landed in staging in #4116 by the sync bot. Then in #4262 a contributor reviewed them and moved them out of staging. Then in #4556 the tests were re-landed in staging by the sync bot. This shouldn't happen, so it's probably something that needs to be fixed in the sync bot.
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 tracing the V8 sync bot behavior involved in issues #4116, #4262, and #4556, comparing the staging state before and after each sync. Identify why tests deliberately moved out of staging were selected again, then verify the fix with a regression test showing that removed tests are not re-synced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100