CI: Increase a range of CVE count to avoid flakes#3415
Merged
Conversation
5 tasks
|
Images are ready for the commit at 6d60f4d. To use with deploy scripts, first |
Member
Author
|
|
theencee
approved these changes
Oct 13, 2022
gavin-stackrox
approved these changes
Oct 13, 2022
Member
Author
|
Looks like the issue is resolved, merging. |
dhaus67
approved these changes
Oct 13, 2022
Contributor
|
/retest |
5 tasks
1 task
1 task
gavin-stackrox
pushed a commit
that referenced
this pull request
Feb 11, 2023
1 task
gavin-stackrox
pushed a commit
that referenced
this pull request
Feb 14, 2023
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
4 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.
Description
Looks the expected CVE range introduced in #2527 is not enough: I've seen "Verify Image Registry+Scanner Integrations" test fail today on most flavours with 181 CVEs.
Increasing the range seems harmless since a reasonable ballpark very likely means a successful test. 0 or 100500 CVE would indicate that something is wrong.
Checklist
Unit test and regression tests addedEvaluated and added CHANGELOG entry if requiredDetermined and documented upgrade stepsDocumented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)Testing Performed
CI run.