Fix benchmark succeeding – even though Benchmark build failed#3502
Merged
fabianfett merged 12 commits intomainfrom Feb 17, 2026
Merged
Fix benchmark succeeding – even though Benchmark build failed#3502fabianfett merged 12 commits intomainfrom
fabianfett merged 12 commits intomainfrom
Conversation
Member
Author
|
This run shows the bad behavior: |
glbrntt
requested changes
Feb 6, 2026
| // MARK: - Benchmarks | ||
|
|
||
| let benchmarks = { | ||
| asdasd |
Contributor
There was a problem hiding this comment.
You should probably remove this bit now 😅
Member
Author
There was a problem hiding this comment.
Obviously reverted now
Member
Author
|
CI run, that proves that this change does, what it shall do: |
simonjbeaumont
requested changes
Feb 11, 2026
glbrntt
approved these changes
Feb 17, 2026
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.
Motivation:
Currently if there is an error in the Benchmark targets, that prevents the Benchmark to build correctly, we still get a CI success.
Modifications:
Result: