Revert "TRT-2549: Revert "Add a serial e2e for accept-risks""#1323
Revert "TRT-2549: Revert "Add a serial e2e for accept-risks""#1323hongkailiu wants to merge 2 commits intoopenshift:mainfrom
Conversation
|
@hongkailiu: This pull request references TRT-2549 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the ticket to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
No actionable comments were generated in the recent review. 🎉 WalkthroughCentralized CVO defaults were added (internal + external packages); code was refactored to use those constants instead of literals; a new end-to-end AcceptRisks test and related test utilities were added; test suite qualifiers and an openshift-tests JSON entry were updated. Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
|
/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-serial-1of2 |
|
@hongkailiu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ed4d9690-0b45-11f1-87fd-e14864a60d45-0 |
The `backup` would not be assigned when the test is skipped earlier in `BeforeEach`. However, `AfterEach` still runs in that case. As a result `CV/version` could be updated with unexpected value. This pull fix the issue by introducing a guard `needRecover` on `AfterEach` which becomes `true` only after `CV` was updated earlier, i.e., it was not skipped.
|
/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-serial-1of2 |
|
@hongkailiu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8131a350-0b4c-11f1-9b6a-01a988e0484f-0 |
|
/payload-aggregate periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-serial-1of2 10 |
|
@hongkailiu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5e192b30-0b6b-11f1-9747-e8748fa3f217-0 |
|
See #1323 (comment) /verified by "TheAggregatedJob" /retest-required |
|
@hongkailiu: This PR has been marked as verified by DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-hypershift-conformance |
|
/lgtm /override ci/prow/e2e-hypershift-conformance |
|
@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-hypershift-conformance DetailsIn response to this:
Instructions 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-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hongkailiu, neisw The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/override ci/prow/e2e-hypershift-conformance |
|
@petr-muller: Overrode contexts on behalf of petr-muller: ci/prow/e2e-hypershift-conformance DetailsIn response to this:
Instructions 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-sigs/prow repository. |
|
@hongkailiu: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
Reverts #1319