Repository navigation
CI: chat-bundle-browser and dashboard-browser shards time out on main #7389
Description
Failing jobs
Main run (push to main, head 0e47330fe57ce5ea1101dae67ee19b836869ef4e, workflow "Python Tests"): https://github.com/loopx-project/loopx/actions/runs/40281869323
Failed browser jobs in that run:
- chat-bundle-browser (1): https://github.com/loopx-project/loopx/actions/runs/40281869323/job/121441461531
- chat-bundle-browser (2): https://github.com/loopx-project/loopx/actions/runs/40281869323/job/121441461583
- chat-bundle-browser (3): https://github.com/loopx-project/loopx/actions/runs/40281869323/job/121441461548
- dashboard-browser (1): https://github.com/loopx-project/loopx/actions/runs/40281869323/job/121441461445
- dashboard-browser (2): https://github.com/loopx-project/loopx/actions/runs/40281869323/job/121441461492
- dashboard-browser (3): https://github.com/loopx-project/loopx/actions/runs/40281869323/job/121441461447
Error
Each failed job ends with TimeoutError and Timeout 30000ms exceeded.. The failing scenario differs by shard:
| Job | Scenario file and line | Waiting on |
|---|---|---|
| chat-bundle-browser (1), dashboard-browser (1) | examples/personal-workspace-browser/conversation-activity.mjs:55:68 |
locator.textContent on .personal-manager-conversation-tray .personal-message-elapsed |
| chat-bundle-browser (2), dashboard-browser (2) | examples/personal-workspace-browser/navigation-sorting.mjs:275:57 |
locator.waitFor on getByText('远端只读投影', { exact: true }) |
| chat-bundle-browser (3), dashboard-browser (3) | examples/personal-workspace-browser/managed-goal-results.mjs:40:57 |
locator.waitFor on getByTestId('goal-declared-objective') |
The runner is invoked from examples/personal-workspace-browser-smoke.mjs:193:24 and :234:1.
Only shard (1) of each suite fails in conversation-activity.mjs.
Reproduces on
- Main run (failing): https://github.com/loopx-project/loopx/actions/runs/40281869323
- PR fix(control-plane): read delegation registry through the refusing loader #7386 run (in progress when checked, browser job conclusions recorded as failure, log output not yet available): https://github.com/loopx-project/loopx/actions/runs/40307999208
- chat-bundle-browser (1): https://github.com/loopx-project/loopx/actions/runs/40307999208/job/121526537204
- chat-bundle-browser (2): https://github.com/loopx-project/loopx/actions/runs/40307999208/job/121526537215
- chat-bundle-browser (3): https://github.com/loopx-project/loopx/actions/runs/40307999208/job/121526537267
- dashboard-browser (1): https://github.com/loopx-project/loopx/actions/runs/40307999208/job/121526537286
- dashboard-browser (2): https://github.com/loopx-project/loopx/actions/runs/40307999208/job/121526537320
- dashboard-browser (3): conclusion success, https://github.com/loopx-project/loopx/actions/runs/40307999208/job/121526537237
Scope note
The same browser jobs fail on main (run 40281869323), with the same TimeoutError signatures, so the logs show these failures on main independent of PR #7386. The PR run logs were not complete when this issue was written, so the PR-side messages are not verified here.
Owners
Mentions: @huangruiteng @songoow. Both are listed on the /examples/ route in .github/CODEOWNERS on main, which matches the failing scenario files.
Activity
[-]CI: conversation-activity browser check times out in chat-bundle-browser and dashboard-browser[/-][+]CI: chat-bundle-browser and dashboard-browser shards time out on main[/+]