Daily verb run RED 2026-09-20: 2 failing verb(s)

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 1mo ago ·closed by John Lauer

Automated daily verb run went red (2026-09-20, exit 1). Scorecard tail:

  fusion_library_parts                       PASS 
  fusion_routing_state#guard                 PASS 
  fusion_route_net#guard                     PASS 
  fusion_routing_drc#guard                   PASS 
  fusion_plan_route#guard                    PASS 
  fusion_schematic#guard                     PASS 
  fusion_schematic#missing                   PASS 
  fusion_make_showcase_project#guard         PASS 
  fusion_eagle_import_status#guard           PASS 
  focus_invariance                           PASS
cleanup: Fusion was already running before the run - leaving it (user's session).

Section coverage (John's product map, 2026-08-14):
  gui-driving                            16 pass / 1 fail (21 manual, 0 skip)  RED
  cad-3d-bom                             13 pass / 1 fail (6 manual, 0 skip)  RED
  mcp-server                             1 pass / 0 fail (1 manual, 0 skip)  green
  python-addin                           6 pass / 0 fail (1 manual, 0 skip)  green
  aps                                    9 pass / 0 fail (13 manual, 0 skip)  green
  auth-tokens                            2 pass / 0 fail (3 manual, 0 skip)  green
  exports                                0 pass / 0 fail (1 manual, 0 skip)  untested-this-tier
  bridge-lifecycle                       11 pass / 0 fail (15 manual, 0 skip)  green

62 PASS, 2 FAIL (65 manual-tier, 0 skipped) -> /home/adom/project/adom-desktop-fusion-bridge/tests/reports/verb-test-2026-09-20_1151.json
  FAIL: fusion_get_app_state - expected success, got error=Fusion main thread busy — document_info running for 10.1s (from another bridge/s code=main_thread_busy
  FAIL: fusion_assembly_bom - expected a BOM or the budget refusal, got error=No active Fusion Design. code=None

Full log: tests/reports/daily-cron-2026-09-20.log on the dev container. Versions at run time are in the readiness line of the log. Triage per dev-skills/fusion-verb-tests: re-run the failing verbs with --only first, a startup race or relay flake re-passes; a repeat failure is the real finding.

1 Reply

John Lauer · 1mo ago

Both failures were test-side, not verb defects. ConfRoomROG's Fusion was mid-operation when the run hit it, so fusion_get_app_state answered main_thread_busy, and the design-info check ran with no Design document active.

Fixed in the runner (1.10.25): a main_thread_busy answer is retried after a settle, and "No active Fusion Design" is accepted as a correct answer for the design-only check when no design is open.

ConfRoomROG has been offline since, so the next green run there is still owed. The same verbs pass on AdomLapper on 1.10.30 today. If tomorrow's run is red again the cron will open a fresh issue with its own scorecard, so closing this one.

John Lauer closed this · 1mo ago