You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem\n\nThe x86 boot path currently reaches marker-only stage advancement without dispatching the staged boot-test registry. This can emit [TESTS_COMPLETE:0/0] / marker-only completion output, so #470 PR-1a must run its x86 frame-custody O2 gate directly from memory initialization and must not claim a staged-suite result.\n\n## Evidence\n\nReview round r3 for #470 observed no [BOOT_TESTS:START] or EarlyBoot staged dispatch on x86. The corrected docker/qemu/run-x86-boot-tests.sh now gates only the direct O2 result and exact [FRAME_CUSTODY_COUNTERS:x86:...] serial vector.\n\n## Required follow-up\n\n- Dispatch registered EarlyBoot/PostScheduler/ProcessContext/Userspace tests at valid x86 contexts.\n- Ensure completion markers are emitted only after a nonzero registered suite actually runs.\n- Remove the #470 direct x86 O2 hook once the registry path is authoritative.\n- Add a harness negative proving 0/0 cannot satisfy the gate.\n- Preserve syscall/interrupt hot-path constraints; do not run blocking staged tests directly from syscall context.\n\nThis is follow-up debt, not part of #470 PR-1a's 230-line production seam.
Problem\n\nThe x86 boot path currently reaches marker-only stage advancement without dispatching the staged boot-test registry. This can emit
[TESTS_COMPLETE:0/0]/ marker-only completion output, so #470 PR-1a must run its x86 frame-custody O2 gate directly from memory initialization and must not claim a staged-suite result.\n\n## Evidence\n\nReview round r3 for #470 observed no[BOOT_TESTS:START]or EarlyBoot staged dispatch on x86. The correcteddocker/qemu/run-x86-boot-tests.shnow gates only the direct O2 result and exact[FRAME_CUSTODY_COUNTERS:x86:...]serial vector.\n\n## Required follow-up\n\n- Dispatch registered EarlyBoot/PostScheduler/ProcessContext/Userspace tests at valid x86 contexts.\n- Ensure completion markers are emitted only after a nonzero registered suite actually runs.\n- Remove the #470 direct x86 O2 hook once the registry path is authoritative.\n- Add a harness negative proving0/0cannot satisfy the gate.\n- Preserve syscall/interrupt hot-path constraints; do not run blocking staged tests directly from syscall context.\n\nThis is follow-up debt, not part of #470 PR-1a's 230-line production seam.