myxce/.wolf/bugs/bug-1902.md
Rongsong Shen 47b9938120
chore(buglog): log bug-1902 (harness pty test timeout seen once, cannot reproduce)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-01 11:23:01 +00:00

53 lines
2.2 KiB
Markdown

---
id: "bug-1902"
status: "cannot-reproduce"
status_updated: "2026-10-01"
status_note: "seen once during task 4.3; passed 5 subsequent runs"
component: "harness"
severity: "noise"
timestamp: "2026-10-01T11:22:43Z"
last_seen: "2026-10-01T11:22:43Z"
occurrences: 1
files: ["src/harness/testsuite/test_test_cli.c"]
tags: ["harness", "test", "flaky", "pty"]
related: []
repro_attempts: "0/5 reruns, 2026-10-01 (4 targeted meson reruns + reviewer full run)"
---
# bug-1902: harness pty test test_source_missing_file_rejected_with_error timed out once after quit
## Description
**Observed:** during task 4.3 of spec job-array-one-based-index, one run of the harness suite under ASAN failed in the pty CLI test:
```
test_test_cli.c: test_source_missing_file_rejected_with_error: FAIL: xce_test did not exit within the harness's safety timeout after 'quit'
```
**Expected:** after `quit`, `xce_test` exits within the test's safety timeout and the test passes, as it does in every other run.
**Impact:** noise: an intermittent false failure of the harness suite; no product impact observed.
**Found by:** test (harness suite run during task 4.3, 2026-10-01)
## Environment
- OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
- libc: glibc 2.42-47 (interpreter /nix/store/wb6rhpznjfczwlwx23zmdrrw74bayxw4-glibc-2.42-47/lib/ld-linux-x86-64.so.2)
- Toolchain: gcc (GCC) 15.2.0, meson 1.9.1
- Build: asan (src/build.jai)
- Code: scheduler-framework @ 1812a80d-dirty (task 4.3 in progress)
- Deployment: none (harness_unit_test, pty-driven xce_test, no controller)
## Reproduction
1. `bash src/tools/xce-build.sh harness asan build.jai --jobs 8 --incremental` (runs the harness suite, including `test_test_cli.c` over a pty)
- Frequency: 1/6 runs, 2026-10-01 (passed in 4 targeted reruns and in the reviewer's run)
- Evidence: not kept (the failing build log was overwritten by the passing reruns)
## Root cause
TODO: required for fixed/partial
## Fix
TODO: required for fixed/partial
## Verification
- Test: TODO: name + file; RED before the fix, GREEN after
- Suites: TODO: suite results and build profile
- Live: TODO: soak/deploy run, or n/a and why
## References
- Related: none