lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(buglog): bug-1553 and bug-1580 cannot-reproduce (0/26 runs)

Browse source 
bug-1580's evidence was a ':FAIL:' grep that cannot match Unity's
colored FAIL lines.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-09-30 03:23:24 +00:00
parent 2d4b893d75
commit fd61721bab
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
3 changed files with 24 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

9
.wolf/bugs/bug-1553.md
View file

@ -1,8 +1,8 @@
---
id: "bug-1553"
status: "open"
status_updated: "2026-09-24"
status_note: "intermittent (~1 in 3) controller_unit_test SIGSEGV; not isolated, re-seen 5bf123cc"
status: "cannot-reproduce"
status_updated: "2026-09-30"
status_note: "0/26 controller_unit_test runs crashed on dc94da20, 2026-09-29; likely fixed by a later race fix (bug-1733?)"
component: "controller"
severity: "crash"
timestamp: "2026-08-13T07:35:00Z"
@ -11,6 +11,7 @@ occurrences: 1
files: ["src/controller/testsuite/ (combined binary", "crash site not yet isolated -- occurs after test_drive_async_config.c's liveness_reserved_* tests)"]
tags: ["flaky", "segfault", "controller_unit_test", "order-dependent", "unity"]
related: []
repro_attempts: "0/26 runs, 2026-09-29 (20 standalone ASAN_OPTIONS=detect_leaks=0 + 6 full-suite via xce-build.sh, dc94da20, asan)"
legacy: true
---
@ -19,6 +20,8 @@ legacy: true
## Description
controller_unit_test (combined 1095-test Unity binary) segfaults intermittently (~1 in 3 full runs observed) somewhere between test_drive_async_config.c and the next testsuite file (test_configcompare.c/test_slowlane.c area) -- no assertion failure, no ASAN report captured before the crash, process just dies (exit 139/SIGSEGV)
UPDATE (2026-09-30): Not seen since August. On 2026-09-29 (dc94da20 + cfa0a941, asan) controller_unit_test ran 26 times -- 20 standalone runs (ASAN_OPTIONS=detect_leaks=0) plus 6 full-suite runs via xce-build.sh -- all exit 0, 1256/1258 Tests 0 Failures, no SIGSEGV. At the recorded ~1-in-3 rate, 20 clean standalone runs in a row has probability ~0.03%. Suspected (not proven): fixed by one of the thread-lifetime/race fixes landed since, most plausibly bug-1733 (42e1eeaa, 2026-08-29: vtask_enq wrote task->owner after publishing the task, a use-after-free that would surface as a bare SIGSEGV outside ASAN), or bug-1839/bug-1851 (controller UAFs, Sep 22/24). Proving which would need a build of an August commit reproducing ~1/3 and bisecting.
## Environment
_Not recorded (migrated from buglog.json)._

9
.wolf/bugs/bug-1580.md
View file

@ -1,8 +1,8 @@
---
id: "bug-1580"
status: "open"
status_updated: "2026-09-24"
status_note: "intermittent controller_unit_test \"2 Failures\" with all cases PASS; not investigated"
status: "cannot-reproduce"
status_updated: "2026-09-30"
status_note: "0/26 runs with failures on dc94da20, 2026-09-29; original ':FAIL:' grep cannot match Unity's colored FAIL lines"
component: "controller"
severity: "crash"
timestamp: "2026-08-18T10:39:52Z"
@ -11,6 +11,7 @@ occurrences: 1
files: ["src/controller/testsuite/ (combined controller_unit_test binary; discovered running xce-build.sh all for the resource-value-verification bug-1579 follow-up fix -- zero C files touched this session", "confirmed via git status)"]
tags: ["flaky", "controller_unit_test", "unity", "aggregate-count-mismatch", "pre-existing"]
related: ["bug-1553"]
repro_attempts: "0/26 runs, 2026-09-29 (20 standalone + 6 full-suite, dc94da20, asan)"
legacy: true
---
@ -19,6 +20,8 @@ legacy: true
## Description
meson test 'xce:controller / controller test' (controller_unit_test) reports '1104 Tests 2 Failures 0 Ignored' / exit status 2, but grep of the full raw testlog for ':FAIL:' or a per-test [FAIL] marker finds ZERO matches -- every individual Unity test case visibly printed PASS. Reproduced deterministically 2/2 times (once via meson test, once via a direct standalone re-run of the binary with ASAN_OPTIONS=detect_leaks=0), unlike bug-1553's documented ~1-in-3 intermittent SIGSEGV (exit 139) signature -- this is exit 2 with no crash indication, a distinct manifestation.
UPDATE (2026-09-30): The original evidence does not hold: controller_unit_test prints colored Unity output, where a failure line is `file:line:test:\e[41mFAIL\e[0m: msg`. A grep for `:FAIL:` can never match it, so "2 Failures but zero FAIL markers" most likely meant two ordinary test failures the grep could not see, not a counter desync; the original log was not kept, so which tests is unknown. On 2026-09-29 (dc94da20 + cfa0a941, asan) controller_unit_test ran 26 times (20 standalone, 6 via xce-build.sh): every run exit 0, 0 Failures, and the printed per-test results agree with the summary. To look for failures in these logs, grep for `FAIL` (or strip ANSI codes first), not `:FAIL:`.
## Environment
_Not recorded (migrated from buglog.json)._