Add triggerScan call to configmanagement integration tests which depend on it#2799
Merged
pedrottimark merged 1 commit intomasterfrom Aug 24, 2022
Merged
Add triggerScan call to configmanagement integration tests which depend on it#2799pedrottimark merged 1 commit intomasterfrom
pedrottimark merged 1 commit intomasterfrom
Conversation
bab5d74 to
f62cf67
Compare
|
Images are ready for the commit at c03e28a. To use with deploy scripts, first |
f62cf67 to
c03e28a
Compare
Contributor
Author
|
/retest-required |
|
@pedrottimark: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Contributor
Author
|
/test gke-ui-e2e-tests |
Merged
2 tasks
2 tasks
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
13 tests in 5 files under configmanagement fail intermittently since cypress 10.6.0 upgrade, for example:
Failing tests
Analysis
The failing tests assume that scan results are available.
'should scan for compliance data from the Dashboard page'from the first test So far, cypress does run tests in alphabetical order.The following lines are filtered and stream edited from build-log.txt files.
cypress 9
1560369927628525568 from master build for Fix scope lookups in image and cluster Vulnerabilities sub-resolvers #2715 on 2022-08-18 which has unrelated failure
cypress 10
1561658257045458944 from master build for Upgrade cypress 10.6.0 devDependencies in ui #2743 on 2022-08-22
1561807085534973952 from master build for Bump k8s.io/apiserver from 0.23.9 to 0.23.10 #2781 on 2022-08-23
from master build for ROX-9766: Add severity column to Image CVEs and Node CVEs tables #2768 on 2022-08-22 which has unrelated failures
Changed files
Export
triggerScanfunction which makestriggerScanrequest and waits on response.Call
triggerScanfunction in first test which assumes that scan results are available.Checklist
Testing Performed
Run test files locally (with teardown and deploy-local between each run to clear the scan results).
See that tests fail before changes and pass after changes:
'should show the same number of low severity policies in the "Policy Violations By Severity" widget as it does in the Policies list'