Support labels in pxr_register_test#4054
Open
nvmkuruc wants to merge 1 commit intoPixarAnimationStudios:devfrom
Open
Support labels in pxr_register_test#4054nvmkuruc wants to merge 1 commit intoPixarAnimationStudios:devfrom
pxr_register_test#4054nvmkuruc wants to merge 1 commit intoPixarAnimationStudios:devfrom
Conversation
5 tasks
Collaborator
|
Filed as internal issue #USD-12136 (This is an automated message. See here for more information.) |
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.
Description of Change(s)
ctestoffers labels as a way to group tests for downstream runners. This introduces support for test labeling and adds a single labelflaky, implying that the test occasionally fails but usually succeeds on retry.The initial set of flaky tests were identified by looking through recent pipeline logs for failures that appeared spurious. The
worktests have been known to fail occasionally for most of the repos lifetime.Future PRs may contribute additional labels (such as those used in regex-based exclusion rules in the CI pipelines).
Example usage:
Link to proposal (if applicable)
aousd/build-ig-initiatives#18
Fixes Issue(s)
Checklist
I have created this PR based on the dev branch
I have followed the coding conventions
I have added unit tests that exercise this functionality (Reference:
testing guidelines)
I have verified that all unit tests pass with the proposed changes
I have submitted a signed Contributor License Agreement (Reference:
Contributor License Agreement instructions)