Summary
AdCP storyboard runner — v3 reference seller (translator) fails on unmodified main. The seller process never becomes ready inside the 30s boot window:
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
Seller failed to start within 30s
##[error]Process completed with exit code 1.
The failure is in the Boot v3 reference seller (translator) step. The upstream-still-alive probe never runs — the readiness loop times out first — so the Node mock server is not implicated.
Evidence that it is main, not a PR
Reproduced on a79e29a2 (current main) with no changes applied, by pushing main unmodified to a fork and letting the same workflow run:
It also failed three consecutive times on #980, a test-only PR that touches nothing outside tests/conformance/, including on an isolated job re-run.
Why it looks like a regression rather than a flake
That leaves a change in the seller's own boot path, a transitive Python dependency resolved at install time, or the runner image, as the likely causes.
Suggested next step
The 30s budget also has no diagnostic on timeout — the step reports only "failed to start" and discards the seller's stdout/stderr, which is why the cause is not visible in the log. Dumping the captured seller log on timeout would make this self-diagnosing, independent of the underlying regression.
Summary
AdCP storyboard runner — v3 reference seller (translator)fails on unmodifiedmain. The seller process never becomes ready inside the 30s boot window:The failure is in the
Boot v3 reference seller (translator)step. The upstream-still-alive probe never runs — the readiness loop times out first — so the Node mock server is not implicated.Evidence that it is
main, not a PRReproduced on
a79e29a2(currentmain) with no changes applied, by pushingmainunmodified to a fork and letting the same workflow run:AdCP storyboard runner — v3 reference seller (translator): failureIt also failed three consecutive times on #980, a test-only PR that touches nothing outside
tests/conformance/, including on an isolated job re-run.Why it looks like a regression rather than a flake
maincontrol — four consecutive failures, no passes.ADCP_SDK_VERSION: latest, and@adcp/sdklatestis still12.1.1(published 2026-07-26, unchanged since before the last green run). The13.0.0-rc.*series published 2026-07-27/28 sits on the separatercdist-tag, so it should not be reaching this job — worth confirming nothing resolves it transitively.That leaves a change in the seller's own boot path, a transitive Python dependency resolved at install time, or the runner image, as the likely causes.
Suggested next step
The 30s budget also has no diagnostic on timeout — the step reports only "failed to start" and discards the seller's stdout/stderr, which is why the cause is not visible in the log. Dumping the captured seller log on timeout would make this self-diagnosing, independent of the underlying regression.