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

docs(buglog): bug-1924 clock test fails when the test PID contains 1999

Browse source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-08 09:31:10 +00:00
parent 54f9139e77
commit 90d417bb1b
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
2 changed files with 81 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
.wolf/buglog.json
View file

@ -17453,6 +17453,30 @@
"record": ".wolf/bugs/bug-1923.md",
"gitea_issue": 348,
"gitea_synced_status": "fixed"
},
{
"id": "bug-1924",
"status": "open",
"status_updated": "2026-10-08",
"status_note": "newly logged",
"component": "scheduler",
"severity": "noise",
"timestamp": "2026-10-08T09:30:37Z",
"last_seen": "2026-10-08T09:30:37Z",
"occurrences": 1,
"error_message": "scheduler core clock test fails when the test PID contains 1999 (tlog line includes getpid())\n\n**Observed:** \"scheduler core clock test\" failed once in a full scheduler gate run (task 2.2 of scheduler-sim-decision-trace, 2026-10-08), then passed 5/5 on rerun:\n```\n../scheduler/testsuite/test_clock.c:351:test_tlog_format_shows_frozen_virtual_time_not_infotime:FAIL: formatted log line must NOT show info->time's wall-clock year while the virtual clock is frozen\n15 Tests 1 Failures 0 Ignored\n```\n**Expected:** the test passes on every run. The formatter output is correct; only the assertion is too broad.\n**Impact:** noise only. A random, rare failure of the scheduler suite (and of `/xce-build scheduler`) that has nothing to do with the change under test, costing a rerun and an investigation. No production effect.\n**Found by:** spec task scheduler-sim-decision-trace 2.2 (full-suite gate run).\n\nThe test sets `info->time.year = 1999` and asserts `strstr(buff, \"1999\") == NULL` over the WHOLE formatted line. `xce_core_tlog_format()` (src/scheduler/src/core_clock.c:238-275) prints `[%5d]` with `getpid()` in that line, and the frozen virtual time (2033-05-18 03:33:20,000) is constant. So the assertion fails whenever the test process's PID contains the digits \"1999\" (e.g. 2619991). Confirmed by forcing such a PID (see Reproduction).",
"file": "src/scheduler/testsuite/test_clock.c",
"root_cause": "TODO: required for fixed/partial",
"fix": "TODO: required for fixed/partial\n\nVerification:\n- Test: TODO: name + file; RED before the fix, GREEN after\n- Suites: TODO: suite results and build profile\n- Live: TODO: soak/deploy run, or n/a and why",
"tags": [
"test",
"flaky",
"clock",
"tlog"
],
"related_bugs": [],
"fix_commits": [],
"record": ".wolf/bugs/bug-1924.md"
}
]
}