test: expand CRC postsubmit E2E with tiered smoke / standard / extended coverage - #2296
Open
fjglira wants to merge 8 commits into
Open
test: expand CRC postsubmit E2E with tiered smoke / standard / extended coverage#2296fjglira wants to merge 8 commits into
fjglira wants to merge 8 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2296 +/- ##
==========================================
+ Coverage 87.88% 88.03% +0.15%
==========================================
Files 56 56
Lines 2658 2658
==========================================
+ Hits 2336 2340 +4
+ Misses 322 318 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
Author
|
We need to wait until: #2294 is merged to be able to retest linter |
…tion in the same job Add tiered CRC E2E coverage with smoke, standard, and extended tiers on a single OpenShift Local cluster. Introduce crc Ginkgo labels, crc-e2e-ci.sh entry point, and sequential steps that reuse the operator deployment. Signed-off-by: Francisco Herrera <fjglira@gmail.com>
Signed-off-by: Francisco Herrera <fjglira@gmail.com>
Signed-off-by: Francisco Herrera <fjglira@gmail.com>
Signed-off-by: Francisco Herrera <fjglira@gmail.com>
…clusion Signed-off-by: Francisco Herrera <fjglira@gmail.com>
Signed-off-by: Francisco Herrera <fjglira@gmail.com>
Signed-off-by: Francisco Herrera <fjglira@gmail.com>
Signed-off-by: Francisco Herrera <fjglira@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
What type of PR is this?
What this PR does / why we need it:
This PR adds tiered CRC E2E coverage to the postsubmit workflow. The operator is deployed once on a single OpenShift Local cluster; later steps reuse it and clean up mesh resources between tiers to stay within CRC memory limits and extend the coverage.
The postsubmit job now runs extended; this extends the current coverage as much as we can on a CRC cluster:
~76 specs vs ~42 before. Most excluded tests are due to CRC memory limits on the GitHub Actions free-tier VM.
Changes done:
tests/e2e/crc-e2e-ci.sh— tier entry point with mesh cleanup between steps.github/workflows/crc-e2e-sail.yaml— postsubmit defaults toextended;workflow_dispatchcan pick any tiercrclabels on E2E suites + Ginkgo filters per tierCreateIstio/CreateZTunnelhelpers and CI env varsCRC exclusions (still run on full OCP E2E):
ambient-targetref-override,library-upgrade,tls-profileNote: CRC E2E remains post-submit only and is not a required branch-protection check.
Which issue(s) this PR fixes:
Fixes #
Related Issue/PR #
Additional information: