Skip to content

docs(roadmap): file the macOS-only background-notice flake; close out session C - #20

Merged
itsdestin merged 1 commit into
masterfrom
docs/session-c-followup
Sep 2, 2026
Merged

docs(roadmap): file the macOS-only background-notice flake; close out session C#20
itsdestin merged 1 commit into
masterfrom
docs/session-c-followup

Conversation

@itsdestin

Copy link
Copy Markdown
Owner

Follow-up to youcoded-dev#19 and youcoded#384 (both merged).

One new roadmap entry. youcoded#384's CI went green on Ubuntu, Windows and the Android leg and red on macOS:

FAIL tests/native-session-host.test.ts > G-1 background Bash > a finished run is injected ONCE …
AssertionError: expected '[Background command sh-4c82 finished …' to match
  /^\[Background command sh-4c82 finished · exit 2 · \d+s\]\n\$ echo done; exit 2\ndone\nFull log: /

Not the branch's doing, established three ways: the failing test is at line 4969 and every hunk the branch touches in that file is between 2407 and 3631; master's own run 33615851775 five hours earlier failed the same macOS leg on an unrelated suite while Ubuntu and Windows passed; and a plain re-run of the identical commit went success with no code change (317 s on that runner against 37 s locally — the load signature).

Filed rather than fixed, deliberately. The notice arriving without the command's own stdout is either a race in the test or a race in the finished-notice composer — and if it is the latter, a user on a slow machine sees a background command report finished with none of its output. Telling those apart needs a macOS reproduction, which this machine is not, and a guessed fix would hide the second reading.

Handoff updated with both merge commits (da955301, ba0566c) and this evidence.

Verified: node scripts/roadmap-check.mjs --quiet exit 0 · node scripts/audit-anchors.mjs --no-diff → MECHANICAL PASS: OK.

🤖 Generated with Claude Code

https://claude.ai/code/session_01T9SRtMoZJNF4sJrodQa1N1

… session C

youcoded#384 went green on Ubuntu, Windows and Android and red on macOS, on a
test 1,300 lines away from anything the branch touched. A plain re-run of the
identical commit passed. Filed rather than fixed: the notice arriving without
the command's own stdout may be a test race OR a real race in the finished-notice
composer, in which case a user on a slow machine sees a background command report
finished with none of its output. That needs a macOS reproduction to tell apart,
and guessing would hide the second possibility.

Handoff updated with both merge commits and the evidence that the macOS leg was
already flaky on master hours earlier (run 33615851775, sync-spaces-engine).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T9SRtMoZJNF4sJrodQa1N1
@itsdestin
itsdestin merged commit 554ed05 into master Sep 2, 2026
1 check passed
@itsdestin
itsdestin deleted the docs/session-c-followup branch September 2, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant