Skip to content

🤖 tests: flaky Windows backgroundBashDirect 'retrieve output after tools are recreated' (empty output) #5606

Description

@ThomasK33

In tests/ipc/runtime/backgroundBashDirect.test.ts, the test "Background Bash Direct Integration › should retrieve output after tools are recreated (multi-message flow)" failed on Windows in the merge queue. The failure dequeued an unrelated PR (#5601, perf capture cooldown files and docs).

This is the same file as #5593, which #5595 fixed for the migration tests. This test is a different one: it reads a background process's output after the tools are recreated. On Windows the output file may still be empty when the test reads it (Windows background latency, see #5596), or the recreated tools may resolve a different output path.

Fix direction: find out why the output is empty, then make the test wait on a deterministic signal (process exit or an output marker) instead of a fixed delay. Fix the product if the recreated tools can really lose a process's output.

Reported by the perf owner; I checked the run log.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions