docs: record that a new CI gate must be proven able to fail - #181
Merged
Merged
Conversation
The MSan job's -O0 is already documented, but only as a fact. Without the reason attached it reads like a debug leftover, and raising it while tidying build flags is an easy and invisible mistake: at -O1 the optimizer folds a planted uninitialized read away, so the job passes while detecting nothing. States the general rule alongside it -- plant the defect a gate exists to catch and confirm it is reported before trusting the gate. That is how the -O0 requirement was found in the first place, and it is the property that separates a gate from a green checkmark. Documentation only; no code or CI behaviour changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One line in
CLAUDE.md, next to the existing MSan-O0note.Why
The
-O0is already documented, but only as a fact. Without the reason attached it reads like a debug leftover — and raising it while tidying build flags is an easy, invisible mistake: at-O1the optimizer folds a planted uninitialized read away, so the job passes while detecting nothing.What
States the general rule beside it:
That is how the
-O0requirement was found (#172), and it is the property that separates a gate from a green checkmark. The same check caught a genuine misconfiguration in the nightly MSan workflow before it merged (#177).Documentation only — no code or CI behaviour changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_019tVgXeXCcfbHqfMjhufWzd