save wolf status
This commit is contained in:
parent
b0f2aea466
commit
534895c5f6
6 changed files with 451 additions and 4102 deletions
|
|
@ -15785,7 +15785,8 @@
|
|||
},
|
||||
{
|
||||
"id": "bug-1429",
|
||||
"status": "fixed",
|
||||
"status_note": "teardown-order fix (2026-08-30) covered 21 sites; test_config_repl.c (~23 sites) + test_term_safety_adapter.c (5) still unverified, and a 300s TIMEOUT recurred 2026-09-24 near test_commit_barrier_rollout.c's jap fixture",
|
||||
"status": "partial",
|
||||
"status_updated": "2026-09-24",
|
||||
"timestamp": "2026-07-10",
|
||||
"error_message": "controller_unit_test suite TIMEOUT (300s, killed by SIGTERM) during /xce-build controller run immediately after uncommitted edits to persist.c, ha_convergence.c, config_repl.c (delaymgr-inline blocking I/O moved to VTASK_LIVE_BLOCK vtasks with inline-fallback-on-failure). Compile succeeded with zero errors (only pre-existing warnings). meson test summary: Ok:0 Fail:0 Timeout:1. Last test output before the hang was test_demotion_replay_yields_committed_only (test_commit_barrier_reply.c) printing overlayfs-SKIP, followed by a burst of HA FSM / persist_apply_pump_run log lines ending in \"HA quorum lost: connected=0 required=1\", then total silence for the remaining ~294s until SIGTERM. No ASAN/crash report -- looks like a genuine hang/deadlock, not a crash.",
|
||||
|
|
@ -15822,8 +15823,8 @@
|
|||
"bug-1687",
|
||||
"bug-924"
|
||||
],
|
||||
"occurrences": 4,
|
||||
"last_seen": "2026-09-19T09:00:00Z"
|
||||
"occurrences": 5,
|
||||
"last_seen": "2026-09-24T10:51:31Z"
|
||||
},
|
||||
{
|
||||
"id": "bug-1430",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue