web_ci build-and-test hangs indefinitely on main

[polina-c]

Most likely culprit is: #1621

It was merged with failed 'build-and-test'

Summary

web_ci → build-and-test hangs indefinitely during the Run all JS/TS tests step (yarn test:all). The tools/composer (widget-builder) vitest run reports all tests passing (6 files / 32 tests), then prints:

Not implemented: navigation to another Document

…and the process never exits, hanging until the GitHub Actions ~6-hour job timeout kills the run.

This reproduces on main and on every PR (it is independent of the change under test), so it currently blocks a green build-and-test for the whole repo.

Reproduction signature

tools/composer  →  Test Files  6 passed (6)
                →  Tests       32 passed (32)
                →  Not implemented: navigation to another Document
                →  [no further output for ~5 hours, until the job timeout]

Affected runs (all same signature, multiple unrelated branches)

Branch	Hung for	build-and-test job
main	306 min	https://github.com/a2ui-project/a2ui/actions/runs/27434536520/job/81093018459
refactor_actions	308 min	https://github.com/a2ui-project/a2ui/actions/runs/27434471660/job/81092795255
dependabot/npm_and_yarn/...-24c5ad6f63	309 min	https://github.com/a2ui-project/a2ui/actions/runs/27435057424/job/81094765314
dependabot/npm_and_yarn/...-d1806c4ab8	304 min	https://github.com/a2ui-project/a2ui/actions/runs/27435354679/job/81095770890
refactor_actions (earlier)	132 min	https://github.com/a2ui-project/a2ui/actions/runs/27389047490/job/80942414373
samples-reorg (PR #1628, cancelled)	hung	https://github.com/a2ui-project/a2ui/actions/runs/27449354106/job/81141212966
samples-reorg (PR #1628, re-run, cancelled)	hung	https://github.com/a2ui-project/a2ui/actions/runs/27449354106/job/81144865534

Last known green build-and-test (before the regression): https://github.com/a2ui-project/a2ui/actions/runs/27428052847 (21 min).

Culprit / when it started

Triggered by #1621 ("ci: refactor GitHub Actions pipeline to use composite actions and consolidated CI workflows", commit eb9d5ffb), merged 2026-06-12 18:18 UTC. main's first hanging build-and-test run started at that same timestamp (run 27434536520).

#1621 deleted the dedicated composer_build_and_test.yml workflow and consolidated everything into web_ci.yml's build-and-test job, which now runs yarn test:all (all workspaces, including tools/composer). That is what pulled the composer jsdom test hang into the shared web CI path repo-wide. The underlying open-handle in the composer tests is the deeper cause (see below), but #1621 is what exposed it as a blocking failure for main and every PR.

Likely root cause

tools/composer runs its tests under the jsdom environment (tools/composer/vitest.config.ts). Its components navigate via Next.js routing / anchor links — e.g. <a href="/widget/${id}"> in src/components/layout/sidebar-widgets.tsx and router.push(...) in src/components/main/create-widget.tsx and src/app/gallery/page.tsx. When a test exercises one of these, jsdom logs Not implemented: navigation to another Document and an open handle (jsdom env / Monaco / CopilotKit / a timer) keeps the Node process alive, so vitest run reports success but never terminates.

Suggested directions

• Stub navigation in tools/composer/src/test/setup.ts (mock window.location / Next.js useRouter so component clicks don't trigger a real jsdom navigation), and/or
• Detect/close the open handle (run vitest run --reporter=verbose with open-handle detection locally to identify it), and/or
• As a stopgap, add a job-level timeout-minutes to web_ci so a hang fails fast (minutes) instead of consuming a ~6h runner.

Impact

Blocks a passing build-and-test check on main and all PRs.

[ditman]

Thanks for creating this. I've seen this issue in an unrelated Lit PR. I think the problem was updating "vite" to version 8.

I'll try to downgrade vite to the previous version to unblock the tree.

It was merged with failed 'build-and-test'

🤦

[ditman]

After some bisecting, I'm getting this:

...
git bisect bad
85381fcc3d366d158396bd9bfbb765f3376923ee is the first 'bad' commit
...

[gspencergoog]

Are you sure it never exits? I've seen times of 20 minutes, but it did finally finish.

I was looking for ways to improve the times.

EDIT: Ahh, I see. five hours is way too long.

[ditman]

I'm seeing several unrelated errors that may have been introduced at the same time:

1. the Lit a2ui_explorer is not working
   • downgrading to "vite": "^7.1.11" seems to do the trick
2. the Angular a2ui_explorer is not working
   • I'm currently bisecting this one bisect points at the same revision
     • Reverting the changes to renderers/angular/tsconfig.json fix its a2ui_explorer app.

Maybe others?

[gspencergoog]

I did also update the versions of packages right before then, in #1616

[ditman]

@polina-c @gspencergoog the "Not implemented" thing is a red herring, I just got the test to pass with that warning message:

dit@dit:/work/google/a2ui/tools/composer$ yarn test
6:51:28 PM [vite] warning: `esbuild` option was specified by "vite:react-babel" plugin. This option is deprecated, please use `oxc` instead.
6:51:28 PM [vite] warning: `optimizeDeps.esbuildOptions` option was specified by "vite:react-babel" plugin. This option is deprecated, please use `optimizeDeps.rolldownOptions` instead.
Both esbuild and oxc options were set. oxc options will be used and esbuild options will be ignored. The following esbuild options were set: `{ jsx: 'automatic', jsxImportSource: undefined }`

 RUN  v4.1.2 /work/google/a2ui/tools/composer

 ✓ src/lib/json-parser.test.ts (10 tests) 9ms
 ✓ src/lib/storage.test.ts (5 tests) 9ms
 ✓ src/contexts/widgets-context.test.tsx (4 tests) 97ms
 ✓ src/components/editor/data-panel.test.tsx (6 tests) 93ms
 ✓ src/components/editor/widget-editor.test.tsx (4 tests) 97ms
Not implemented: navigation to another Document
 ✓ src/components/editor/editor-header.test.tsx (3 tests) 94ms

 Test Files  6 passed (6)
      Tests  32 passed (32)
   Start at  18:51:28
   Duration  1.50s (transform 440ms, setup 473ms, import 1.14s, tests 401ms, environment 4.51s)

✅ Ran 2 scripts and skipped 4 in 77.7s.

I was able to run most tests locally after git revert 85381fcc3d366d158396bd9bfbb765f3376923ee

The problem is #1616, we need to revert that. Unfortunately that's not super easy to do now because #1628 landed too.

I'll try to post a CL with a couple of revert commits to see if the tree gets greener.