ci: Run only unit tests and tolerate performance benchmarks#9
Merged
Conversation
The default unit test step ran all CTest labels, including performance benchmarks, which fail on shared Debug runners. Run only unit tests and leave the dedicated performance step as best-effort (continue-on-error). Co-Authored-By: Claude <noreply@anthropic.com>
kegouro
force-pushed
the
ci/fix-build-workflow
branch
from
cdb648a to
2653288
Compare
kegouro
changed the title
Set XDG_CONFIG_HOME to a per-process temporary directory so parallel ctest processes do not race on ~/.config/beamlab/<profile>.json. This removes the remaining source of flakiness in SaveUserOverridesCreatesFile. Co-Authored-By: Claude <noreply@anthropic.com>
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.
Fix the
build.ymlworkflow so the unit-test step only runs unit tests and the performance benchmark step does not fail the whole job.The previous
Unit Testsstep ranctestwithout a label filter, so performance benchmarks executed during Debug builds and failed on shared runners. The performance step already existed for Release builds; this change makes it best-effort (continue-on-error: true) so variable runner performance does not block the rest of CI.