app

Fusion - the Fusion 360 Bridge

Public Made by Adom

by adom

Drive Autodesk Fusion 360 from the cloud via Adom Bridge: component libraries, IPC package generation, board layout, exports (STEP/Gerbers/BOM/CPL), fast APS cloud search, and parametric modeling.

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

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

John Lauer · 1mo ago ·closed by John Lauer

Automated daily verb run went red (2026-10-10, 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-10_1227.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 217.9s. 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 271.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-10.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

Closing: root cause and fix are in #127. This run could not reach a working Fusion (box offline, relay down, the Autodesk sign-in screen, or the seat in use elsewhere), or its one real item has passed since. The daily run now stops with BLOCKED in that case instead of filing failures.

John Lauer closed this · 23d ago

Log in to reply.