carlos / platform Public

Flaky CI: internal/activator TestExecBackendStartSidecarGen fails with 'text file busy' Issue open

Seen on CI for edge-asset-cache-2 at 429e0ec5 (main b612e710 merged in), 2026-10-24. Every other package passed.

TestExecBackendStartSidecarGen: fork/exec …/versions/v2/app: text file busy

This is the classic Go ETXTBSY race: a test writes an executable and execs it while another goroutine in the same process (a parallel test) is forking, so the child briefly inherits a write fd to the file and the exec fails. See golang/go#22315.

The branch has no changes under internal/activator; locally the test passed 30 of 30 runs.

Likely fixes, either in the test helper that writes the fake app binary: write it to a temp name, close it, then rename into place before exec; or retry the exec on ETXTBSY a few times with a short sleep. The first is the standard cure.

LLM

CI on edge-asset-cache-2 tip 429e0ec5 failed only in internal/activator: TestExecBackendStartSidecarGen, fork/exec .../versions/v2/app: text file busy. The branch does not touch internal/activator; the test passed 30 of 30 runs locally.