Daily verb run RED 2026-10-19: 21 failing verb(s)

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

Closed general

John Lauer · 24d ago ·closed by John Lauer

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

  exports                                0 pass / 0 fail (1 manual, 0 skip)  untested-this-tier
  bridge-lifecycle                       12 pass / 0 fail (15 manual, 0 skip)  green

46 PASS, 21 FAIL (80 manual-tier, 0 skipped) -> /home/adom/project/adom-desktop-fusion-bridge/tests/reports/verb-test-2026-10-19_1226.json
  FAIL: fusion_account - expected success, got error='fusion_account' did not respond within ab's 60s budget. code=timed_out; missing field 'holdsSeat'; missing field 'running'
  FAIL: fusion_get_app_state - expected success, got error=Main thread busy — activity_banner running for 118.2s. code=main_thread_busy
  FAIL: fusion_get_preferences - expected success, got error='fusion_get_preferences' did not respond within ab's 25s budget. code=timed_out; missing field 'current'
  FAIL: fusion_set_preference - expected success, got error='fusion_set_preference' did not respond within ab's 40s budget. code=timed_out
  FAIL: fusion_assembly_bom - expected a BOM or the budget refusal, got error='fusion_assembly_bom' did not respond within ab's 60s budget code=timed_out
  FAIL: fusion_open_cloud_file - expected success, got error=None code=None; timed out
  FAIL: fusion_show_schematic - expected success, got error='fusion_show_schematic' did not respond within ab's 60s budget. code=timed_out
  FAIL: fusion_show_2d_board - expected success, got error='fusion_show_2d_board' did not respond within ab's 60s budget. code=timed_out
  FAIL: fusion_board_info - expected success, got error=Add-in request failed: http://127.0.0.1:8774/command: Network Error: Network Err code=None; missing field 'rawXml'
  FAIL: fusion_open_electronics - expected success, got error=Add-in request failed: http://127.0.0.1:8774/command: Network Error: Network Err code=None; missing field 'isElectronics'
  FAIL: fusion_list_text_commands - expected success, got error=Add-in request failed: http://127.0.0.1:8774/command: Network Error: Network Err code=None; missing field 'commands'
  FAIL: fusion_execute_text_command - expected success, got error='fusion_execute_text_command' did not respond within ab's 60s budget. code=timed_out
  FAIL: fusion_show_3d_board - expected success, got error='fusion_show_3d_board' did not respond within ab's 60s budget. code=timed_out
  FAIL: fusion_inspect_bodies - expected success, got error='fusion_inspect_bodies' did not respond within ab's 60s budget. code=timed_out; missing field 'bodies'; missing field 'units'
  FAIL: fusion_physical_properties - expected success, got error='fusion_physical_properties' did not respond within ab's 60s budget. code=timed_out
  FAIL: fusion_get_design_info - expected success, got error=Add-in request failed: http://127.0.0.1:8774/command: Network Error: Network Err code=None
  FAIL: fusion_get_parameters - expected success, got error=Add-in request failed: http://127.0.0.1:8774/command: Network Error: Network Err code=None
  FAIL: fusion_document_info - expected success, got error=Main thread busy — activity_banner running for 102.1s. code=main_thread_busy
  FAIL: fusion_run_modeling_script#guard - expected errorCode=wrong_document got timed_out (error='fusion_run_modeling_script' did not respond within ab's 180)
  FAIL: fusion_assembly_bom#guard - expected errorCode=wrong_document got timed_out (error='fusion_assembly_bom' did not respond within ab's 60s budget)
  FAIL: fusion_run_modeling_script - expected success, got error='fusion_run_modeling_script' did not respond within ab's 180s budget. code=timed_out

Full log: tests/reports/daily-cron-2026-10-19.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 · 23d ago

Root cause: the test box could not run Fusion, so these were not bridge failures. Since Oct 7, ConfRoomROG's Fusion has been at the Autodesk sign-in screen (Oct 17) or behind the "Active Sessions Exceeded" seat dialog (every other day). The one Autodesk seat was in use on another machine. Fusion answers nothing in that state, so each verb timed out and the run filed about 21 "failures" a day. Checked live today: fusion_readiness on ConfRoomROG reports licensingDialog: true, and the box was last ready on 2026-10-17 11:58.

What changed (tests only, so there is no release and nothing to install): the run now has a preflight gate.

It gives fusion_readiness two minutes to clear the dialog, which it does automatically when it can.
If Fusion is still behind the seat dialog or at the sign-in screen, the run stops with BLOCKED (exit 3) and the cause, and scores nothing.
The cron then keeps one standing "Daily verb run BLOCKED" issue and adds a line to it each day, instead of a new red issue every morning.
A red issue now means a real failure.

Tested against ConfRoomROG twice: it stopped with BLOCKED, exit 3, after about three minutes.

The older reports, checked one by one:

#106, #107 and #114: the box was offline (target_not_found).
#118: the relay was down. Its two real-looking items, the deprecated cloud-search verbs not refusing, have passed every day since Oct 16.
#110: four new routing verbs were missing from the test plan; they were added since.
Every other report is this seat or sign-in block.

Closing them all. The daily run turns green again once ConfRoomROG holds the seat. The seat is shared with arav-rog, where testing and other people's work happen, so whether the daily box takes it every morning is John's decision, not something the run should do on its own.

John Lauer closed this · 23d ago