AI_Assistant/pcbjam
Watch
1
0
Fork
You've already forked pcbjam
 0
Code Issues Pull requests Projects Releases 7 Packages Wiki Activity Actions

test(web): wait out the boot overlay before clicking Tools — assign-footprints flake

Browse source 
The spec's boot gates (canvas, registry, title) are all wx-side and go
live seconds before WasmTool drops its opaque boot overlay (ready only
flips after the collab seed + waitForWxUi). The Tools click landed on
the overlay, the popup never opened, and the menu-item wait timed out —
flaky on CI (the 1s title poll sometimes samples after overlay unmount),
100% locally. Add the inset-0.z-30 count-0 guard the chrome-toggle /
tool-switch / quit-* specs already use.

Verified: web-chromium 5/5, web-firefox 8/9 (was 0/5, 0/1). The one
remaining firefox failure is a distinct pre-existing wasm trap on the
CvPcb-open path (EVT.MENU dispatch → "index out of bounds" in a worker),
same signature as the eeschema-fp-selector CI trap — now known to
reproduce on macOS real GL too. Left as a TODO(cvpcb-open-trap) in the
spec; needs a debug-symbol repro.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rb9jsqtHsC3tHTaJ45244j
This commit is contained in:
Viktor Vaczi 2026-07-19 18:13:44 +02:00
commit f3b43c831f
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
tests/web/eeschema-assign-footprints.spec.ts
View file

@ -91,6 +91,12 @@ test('Tools → Assign Footprints opens CvPcb (merged third kiface)', async ({ p
await expect await expect
.poll(() => page.title(), { timeout: 150000, intervals: [1000] }) .poll(() => page.title(), { timeout: 150000, intervals: [1000] })
.toMatch(/Schematic Editor/i); .toMatch(/Schematic Editor/i);
// The wx UI (canvas, registry, title) is live seconds BEFORE WasmTool drops
// its opaque boot overlay — `ready` only flips after the collab seed +
// waitForWxUi. A click in that window lands on the overlay, the Tools popup
// never opens, and the menu-item wait below times out. Same guard as
// chrome-toggle.spec.ts: boot + lib fat-load overlays are both `inset-0 z-30`.
await expect(page.locator('div.inset-0.z-30')).toHaveCount(0, { timeout: 150000 });
await page.screenshot({ path: SHOT('01-boot'), scale: 'css' }); await page.screenshot({ path: SHOT('01-boot'), scale: 'css' });
expect(await clickMenuBarItem(page, 'Tools'), 'Tools menu opened').toBe(true); expect(await clickMenuBarItem(page, 'Tools'), 'Tools menu opened').toBe(true);
@ -125,6 +131,15 @@ test('Tools → Assign Footprints opens CvPcb (merged third kiface)', async ({ p
} }
}, item); }, item);
// TODO(cvpcb-open-trap): ~1/9 local web-firefox runs die right here — the
// EVT.MENU dispatch traps ("wx_dom_event(48,9) failed" + worker
// "RuntimeError: index out of bounds"), eeschema survives, CvPcb never
// appears, zero libs-bridge calls. Same trap signature as the
// eeschema-fp-selector CI trap (docs/features/web-e2e-rot/01) — which
// reproduced on macOS real GL, so it is NOT llvmpipe-only. Needs a
// debug-symbol repro; post-link binaryen rewriting makes the shipped
// module's DWARF useless for symbolizing the trap offset.
//
// The frame construction + netlist mail runs off wxPostEvent'd follow-ups, // The frame construction + netlist mail runs off wxPostEvent'd follow-ups,
// which the wx WASM port only flushes on input events — wiggle the mouse // which the wx WASM port only flushes on input events — wiggle the mouse
// while polling. (No auto-answering of prompts here: CvPcb itself shows an // while polling. (No auto-answering of prompts here: CvPcb itself shows an