Add information to the errors raised by scorecard basic tests to allow easily identify the scenarios #5273
Conversation
This file contains 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
camilamacedo86
requested review from
jmccormick2001
and removed request for
rashmigottipati and
estroz
…w easily identify the scenarios Signed-off-by: Camila Macedo <[email protected]>
churrodata
approved these changes
Oct 4, 2021
jmccormick2001
approved these changes
Oct 4, 2021
theishshah
approved these changes
Oct 4, 2021
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
Add information to the errors raised by scorecard basic tests to allow easily identify the scenarios
Motivation
I check these needs when I was troubleshooting the errors faced in the tests/ci of this repo or in the CVP pipeline trying to help Operator authors. Without the error message and the cr name is very hard to identify why the scenario is failing.