Clear detail stack in auto-runner#843
Open
ml-physec wants to merge 1 commit into
Open
Conversation
ml-physec
force-pushed
the
fix/detail-stack-clear
branch
from
July 22, 2026 10:08
c437634 to
cd90181
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
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.
🍍
Previously, after a failed test it wouldn't clear the detail stack, so it could grow (up until the limit) if multiple tests failed, leading to any following tests to fail indicating a full detail stack.
Now the detail stack is cleared before each test (when using the automatically generated runner).
For now, I added it where
UNITY_CLR_DETAILSwas called, but it could also make sense to add it in other places, likeresetTest,verifyTestand/orUnityConcludeTest.I also noticed a copy-paste typo when
Push/Popare used withoutUNITY_DETAIL_STACK_SIZEdefined.