e2e typed-reference flaky: no 'utsb: menu settings' after 10 s #98

New issue

Closed

opened 2026-10-28 10:49:05 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-10-28 10:49:05 +00:00

Collaborator

CI run 171 (job 1770, PR #90 at e0ae57f) failed one case and passed on a re-run with no change:

FAIL typed-reference (24s)
  | typed-reference: FAIL: no 'utsb: menu settings ' (x1) after 10 s
e2e: 23 passed, 1 failed, 0 skipped (failed: typed-reference)

That commit changed only Rust install code (sword/src/install/package*) and tests; the case passed on 97f46c2 and locally. The tap on the reading view's ⋮ menu (or its Settings item) seems to get lost now and then. The e2e-logs artifact of that job has the app log. Like #96, a flaky gate costs a >10 min re-run on the single runner.

Likely fix: have e2e_menu retry the tap when the menu's open line doesn't come, or wait on the menu's opened line before tapping the item.

CI run 171 (job 1770, PR #90 at e0ae57f) failed one case and passed on a re-run with no change: ``` FAIL typed-reference (24s) | typed-reference: FAIL: no 'utsb: menu settings ' (x1) after 10 s e2e: 23 passed, 1 failed, 0 skipped (failed: typed-reference) ``` That commit changed only Rust install code (`sword/src/install/package*`) and tests; the case passed on 97f46c2 and locally. The tap on the reading view's ⋮ menu (or its Settings item) seems to get lost now and then. The e2e-logs artifact of that job has the app log. Like #96, a flaky gate costs a >10 min re-run on the single runner. Likely fix: have `e2e_menu` retry the tap when the menu's open line doesn't come, or wait on the menu's opened line before tapping the item.

claude-bot added this to the v0.1 — reader milestone

2026-10-28 10:49:05 +00:00

claude-bot added the

priority

Should

label

2026-10-28 10:49:05 +00:00

claude-bot referenced this issue

2026-10-28 10:50:38 +00:00

Module import from a URL and through Content Hub (#10 part 2c) #90

claude-bot referenced this issue

2026-10-28 10:53:09 +00:00