When the readiness timeout fires, the CLI asks Worker Compose for status.
If Compose has already marked the crashed worker failed, the CLI reports
that failure, including the worker's "could not create its API secret"
error, instead of the generic "not ready after 3s" text. Which message
wins depends on how fast Compose records the exit, so the scenario
failed on unrelated pull requests on both Linux and macOS.
The scenario now accepts either message. It still asserts a non-zero
exit and that the worker log holds the secret error.
Summary
The
inline-worker-fatalstartup scenario in the release gate fails at random on unrelated pull requests (#1661 and #1664, on bothpacked artifactjobs), while main passes.When the 3 s readiness timeout fires, the CLI asks Worker Compose for status (
src/cli.ts, startup failure path). If Compose has already marked the crashed worker failed, the CLI throws that failure, which carries the worker's real error ("agentmemory could not create its API secret ..."). If not, it throws the generic timeout text, which contains3s. The scenario only accepted the second form, so the result depended on how fast Compose recorded the exit.The real cause is the better message for a user, so the scenario now accepts either. It still asserts a non-zero exit and that the worker log holds the secret error.
Changes
expectFailureaccepts a RegExp as well as a string.inline-worker-fatalexpects/3s|could not create its API secret/.Testing
node scripts/release-gate/startup.mjs --tarball <packed> --only inline-worker-fatallocally: PASS.Worker Compose failed: agentmemory: exited unexpectedlywith the secret error, which the new pattern matches.Summary by CodeRabbit