iOS runner: isolate collapsed-tab occupancy test from prerequisite timeouts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 49/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ios, typescript
Research direction
Start with RunnerTests+SnapshotCapturePlanOccupancyTests.swift near line 529 and inspect the test’s fixture and the prerequisite viewport, orientation, keyboard, and tree-processing steps. Build a focused reproduction that detects an unintended prerequisite timeout, then verify the corrected fixture passes while retaining the delayed-operation assertion, expected budget reason, and truncated-tree refusal. Run the owning iOS test lane.
Written by the indexing model from the issue text.
Description
Purpose
Make the collapsed-tab occupancy test exercise its intended exhausted tree tier on slow CI hosts.
testPlanMovesPastATreeTierWhoseCollapsedTabQueryCannotStart expects reason budget. It sometimes receives capture-failed at RunnerTests+SnapshotCapturePlanOccupancyTests.swift:529.
Evidence
The raw job logs show the same assertion on three unrelated heads:
- #3791,
0295ee5f: job 117698966135. - #3798,
7c105337: job 117668259465. - #3785,
449b4d48: job 117419145731.
The test file is identical across these heads. #3791 changes no Swift file. Its new daemon timing step runs after the XCTest suite.
The #3791 log records a one-second snapshot_viewport timeout before private AX recovery. The other failures record a tree-processing timeout. These paths produce capture-failed before the intended budget assertion. Host timing is a suspected trigger; it is not a proven complete cause.
A focused local loop passed 3/3 times on a separate iOS 26.2 simulator. No local red reproduction or fix is proven.
Required behavior
- Isolate prerequisite viewport, orientation, keyboard, and processing work from the deliberately delayed tree operation.
- Preserve the assertion that the delayed operation was entered.
- Preserve the expected budget reason and the refusal to accept a truncated tree as healthy.
- Use a deterministic fixture or injected facts. A warm-up read alone must not claim to prevent a later timeout.
- Do not widen timeouts, add retries, skip the test, or accept both reason codes.
Completion
Show a focused reproduction that detects the unintended prerequisite timeout. Then show the corrected fixture passes and still detects the intended regression. Run the owning iOS lane.
Owner: the iOS runner test lane. Related: #2847 and #2957. Keep this fix separate from #3791's daemon startup contract.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 334
- Avg merge
- 12h 13m
- Merged PRs (30d)
- 723
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from callstack/agent-device
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
callstack/agent-device#3819 ·
Maintainers usually reply within 1 day
-
macOS helper audio-probe always reports -90 dBFS: AVAudioPCMBuffer frameLength set after the copyPossibly taken @jipeng6036-del claimed this today. Openbug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
callstack/agent-device#3771 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
callstack/agent-device#1869 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
callstack/agent-device#3832 ·
Maintainers usually reply within 1 day
-
Android smoke: first fixture capture stalls before any readable snapshotPossibly taken @thymikee claimed this today. Openbug needs-triage
callstack/agent-device#3831 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in callstack/agent-device
Similar issues
-
docs(api): openapi.yaml still documents gif-tools optimize colors as 2-256 instead of 2, 4, 16, 256Openarea: backend documentation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
snapotter-hq/SnapOtter#2919 ·
Maintainers usually reply within 1 day
-
accepted :+1: bug db/redis
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
beekeeper-studio/beekeeper-studio#4882 · 1 comment ·
Maintainers usually reply within 1 day
-
ready-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
konflux-ci/konflux-ui#1630 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ahmedkhaleel2004/gitdiagram#233 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
simkimsia/netlify-axi#19 ·
Maintainers usually reply within 1 day