chore: adding label runner to tests#1434
Merged
MaximilianoUribe merged 5 commits intomainfrom Feb 18, 2026
Merged
Conversation
matthchr
previously approved these changes
Feb 18, 2026
Member
matthchr
left a comment
matthchr
left a comment
There was a problem hiding this comment.
LGTM but I think we may need to cut the GPU scenario
MaximilianoUribe
force-pushed
the
muribefalcon/adding-runner
branch
from
f545f38 to
a6f2f88
Compare
matthchr
approved these changes
Feb 18, 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
2 participants
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.
Fixes #
Description
Adding label runners to tests that would be relevant to include in runners
I went with the label-based approach to avoid code duplication and to make test updates easier. The main trade-off is that we don’t get the full coverage a complete runner suite would provide, but I don’t see a real benefit in maintaining two nearly identical suites in different places
Opening discussion for the tests that are included
How was this change tested?
Does this change impact docs?
Release Note