Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bug(tests): Windows Bash /tmp warnings break Codex and ratchet assertions

Open
  • Is something wrong?
#2,190 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@dnlrsls is already working on this.

Since Oct 28, 2026.

Assessment

This issue has not been assessed yet.

Description

status:approved type:bug
Existing Issue Search
  • I searched existing issues and will add evidence to a canonical tracker when applicable.
📝 Observed Consequence

The native Windows full-module CI suite fails in Codex handoff and ratchet tests whose captured output contains unexpected Bash startup warnings. The existing strict stdout/stderr assertions must remain intact. This is a corrective follow-up related to #1891, not a request for another observer.

🔄 Steps to Reproduce
  1. Existing occurrence: PR #2189, CI run 40728441655, Windows Full Suite (Observational) job 122957914771.
  2. The original default-tag go test -json ./... ran at synthetic merge 07bc5fe716542f148fdf22faab408df9d3d1b6d1 (head ac261105dcb32fbd5b127df74157a2d0e1b7e839; base cf7804bacc8cfea2a3946d8fdd38ca365690410a).
  3. Inspect the failures in TestCodexRegisteredSessionHandoff, TestDeadcodeRatchetToolchain, TestPerfRatchetAgainst and TestPerfRatchetUpdate.
  4. This is an observed hosted occurrence, NOT a deterministic local recipe. One isolated unchanged-main control described below passed without reproducing the warning.
✅ Expected Behavior

Bash children should have usable, correctly owned temporary state throughout their execution, without unexpected startup diagnostics contaminating strict output contracts. Establish the first repository-owned cause and a deterministic regression before approving a fix. Preserve all stderr, exit-code, HTTP and ownership/security assertions, the two-second adapter guard, deadlines, workloads, macOS/Linux behavior, six required checks and merge queue.

❌ Actual Behavior

The job failed: 8540 PASS / 33 FAIL / 127 SKIP. The 33 failures include parent results; there are 26 failing leaves across four top-level tests. All 26 leaf outputs contain the missing-/tmp warning. Ratchet diagnostics retain expected exit semantics but extra warning text breaks output comparisons. Root cause and candidate/base independence are NOT established; no hardware-overload claim is made.

Operating System

Windows

Release Version (Report Context)

Source tests at cf7804bacc8cfea2a3946d8fdd38ca365690410a; Go 1.26.10. No released engram binary was used for this control.

Agent / Client

Other

📋 Relevant Logs
bash.exe: warning: could not find /tmp, please create!

Hosted Windows: 8540 PASS / 33 FAIL (including parents) / 127 SKIP
Failed packages: plugin, scripts

Isolated unchanged-main control, count=1:
TestCodexRegisteredSessionHandoff/resume/multiple_responses PASS (1.38s)
Go exit=0; stderr empty; warning count=0; no skips

https://github.com/Gentleman-Programming/engram/actions/runs/40728441655/job/122957914771

💡 Additional Context

The isolated native Windows control used the pinned main above, existing offline Go 1.26.10/CGO0 and jq 1.8.2, with private profiles/cache removed afterward. It is NOT a RED, fix verification, full-suite result or reproduction of hosted ordering/process context. No repeated attempt is implied.

Duplicate review: #1727/#1748 fixed CombinedOutput JSON-stream contamination, not temporary-state validity. #2179/#2184 cover diagnostics; #2175 covers SessionEnd timeout isolation; #2159 covers curl layout; #2051 concerns detached-server SQLite temp lifetime. None is approval for this correction.

Raw ratchet diff paths/timestamps alone are not an independent confirmed bug: the existing normalizer runs before comparison, and four isolated unchanged-function controls passed. Require a distinct functional RED before any format fix; no generalized scrubbing or warning filtering.

Related to #1891. Do not modify PRs #2164, #2177, #2180, #2185 or #2189. This report does not approve implementation or change issue ownership.

Dominant language
Go
Stars
7.1k
Forks
729
Avg merge
8h 35m
Merged PRs (30d)
319

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Gentleman-Programming/engram

All issues in Gentleman-Programming/engram

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.