Add incident detection UI tests to all 4.19+ configs#75225
Conversation
|
/cc @IshwarKanse |
|
Please rehearse run related jobs |
|
/pj-rehearse |
|
@DavidRajnoha: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm |
|
/pj-rehearse ack |
|
@DavidRajnoha: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-rhobs-observability-operator-main-amd64-ocp-4.20-azure-coo-stage |
|
@lihongyan1: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse |
|
@simonpasquier: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@simonpasquier, |
…onfigs The monitoring-plugin-tests-monitoring-incidents-ui-integration ref was only present in the amd64-ocp-4.19-gcp variant. Add it to the remaining supported release configs (4.20-azure, 4.21-azure, 4.21-gcp-interop) so incident detection coverage matches across all release versions. Co-authored-by: Cursor <cursoragent@cursor.com>
fbb3a97 to
afabac2
Compare
|
/pj-rehearse |
|
@DavidRajnoha: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
WalkthroughThree CI operator configuration files for the rhobs observability-operator were updated to add a new test reference ( Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 10✅ Passed checks (10 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
The failures are not caused by PR #75225. All three jobs show the same pre-existing |
|
/pj-rehearse |
|
@danielmellado: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse |
|
@DavidRajnoha: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
Azure: Azure 4.21: GCP 4.21: @simonpasquier could you lgtm and approve this, as the incident detection test inclusion is working properly? |
|
/lgtm |
|
/pj-rehearse ack |
|
@simonpasquier: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DavidRajnoha, IshwarKanse, simonpasquier 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 |
|
@DavidRajnoha: The following tests 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. |
c9b8e31
into
openshift:main
The monitoring-plugin-tests-monitoring-incidents-ui-integration ref was only present in the amd64-ocp-4.19-gcp variant. Add it to the remaining supported release configs (4.20-azure, 4.21-azure, 4.21-gcp-interop) so incident detection coverage matches across all release versions.
Summary by CodeRabbit