[release-4.22] OCPBUGS-86865: Stabilize ocl 4.22#6115
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: umohnani8 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 |
|
@umohnani8: This pull request references Jira Issue OCPBUGS-86865, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
/jira refresh |
|
@umohnani8: This pull request references Jira Issue OCPBUGS-86865, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
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. |
TestMachineOSConfigChangeRestartsBuild flakes because the build controller (running 3 concurrent workers) races between deleteMachineOSConfig for the previous test's MOSC and addMachineOSConfig for the new test's MOSC. Since both MOSCs share the same name, deleteMachineOSConfig's label-based query matches and deletes MOSBs created by the new MOSC. Fix both the controller and test assertions. Signed-off-by: Urvashi <umohnani@redhat.com>
The sharded tests are now required, we can remove the previous monolithic ocl test suite now. Signed-off-by: Urvashi <umohnani@redhat.com>
…nlyChange The e2e-ocl-2of2 test suite has a 120-minute Go test timeout. Prior tests (each doing full image builds at 10-15 min each plus node rollouts) consume 90-113 minutes depending on CI conditions. TestStaleAnnotationClearedOnLayerOnlyChange runs last and needs ~30 minutes but sometimes only has ~7 minutes left, causing a timeout panic. Bump the timeout from 120m to 150m to provide sufficient headroom. Signed-off-by: Urvashi <umohnani@redhat.com>
d22b587 to
faeab0b
Compare
|
@umohnani8: 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-sigs/prow repository. I understand the commands that are listed here. |
|
/retest |
- What I did
Backport test fixes to stabilize the e2e-ocl tests and remove the monolithic ocl test suite
- How to verify it
CI runs of the sharded tests should be green
- Description for the changelog
stabilize ocl test suite for release-4.22 branch