Flaky e2e: doctor-drift leaves a vanished device 'ready' instead of 'deleted'
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 56/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing-qa
Research direction
Start with e2e/doctor-drift.test.ts, especially the named drift test and the assertion at line 217. Run the test repeatedly with six parallel runs, as described in the issue, and trace how the vanished device's state is determined. Done when the test reliably marks the vanished device deleted rather than ready or recreated.
Written by the indexing model from the issue text.
Description
e2e/doctor-drift.test.ts, 'reports registry vs. reality drift, applies only registry-safe fixes, and skips leased devices'. Error: vanished deviceC should be marked deleted, not recreated: expected 'ready' to be 'deleted' (e2e/doctor-drift.test.ts:217). Reproduces on origin/main f5c796f: 7 of 18 runs failed with 6 runs in parallel (3 rounds of 6). Also seen in CI on PR #394 (run 37442268426). Not caused by #369 (3 of 18 on its branch too, same code path on main).
Written by an agent.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 1
- Avg merge
- 8h 23m
- Merged PRs (30d)
- 136
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from callstackincubator/simlock
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/simlock#424 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
callstackincubator/simlock#422 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 1/5 Under an hour Newbie friendliness 88/100
callstackincubator/simlock#420 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
callstackincubator/simlock#350 · 1 comment ·
Maintainers usually reply within 1 day
-
Flaky e2e: gateway-fleet reads a worker's capacity before the worker has left startingPossibly taken @V3RON claimed this 1 day ago. Openbug:ready flaky-test
Difficulty 4/5 1-2 days Newbie friendliness 48/100
callstackincubator/simlock#414 · 1 comment ·
Maintainers usually reply within 1 day
All issues in callstackincubator/simlock
Similar issues
-
Bump Firebase JS SDK (12.19.0 → 13.0.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
invertase/react-native-firebase#9364 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 4 days
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
redhat-developer/rhdh-plugin-export-overlays#4261 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug] 官网文档的图片挂了Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area:cli bug triage:in-progress
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day