Repository navigation
Keep queue test checks active in Release builds - #67
Merged
Merged
Conversation
rigtorp
force-pushed
the
v2/04b-test-checks
branch
from
November 18, 2026 04:14
2d2f316 to
fae8e9c
Compare
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
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.
Summary
Use SPSCQueue's test-only check macro. Release builds evaluate every check
and keep their normal
NDEBUGsetting when compiling the queue header.Evidence
NDEBUGto keep assertionexpressions active, including calls to queue operations.
-DNDEBUG,an intentionally failing check printed its file and line and aborted.
GCC 14 MC/DC reported 28/28 condition outcomes. Pre-commit passed.
Merge Danger
Door Two-way. The change is isolated to the test source.
Blast radius Test diagnostics and compilation settings.
Stacked on #66.