-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Update and test upstream OTEL jobs #58773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.15-amd64-aws-opentelemetry-e2e-tests |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.15-amd64-aws-opentelemetry-e2e-tests |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/reopen |
@IshwarKanse: Reopened this PR. In 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. |
/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.15-amd64-aws-opentelemetry-e2e-tests |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Add fix PR for monitoring test case open-telemetry/opentelemetry-operator#3458 |
7263d2f
to
8353a63
Compare
/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.15-amd64-aws-opentelemetry-e2e-tests |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Fix failing tests openshift/distributed-tracing-qe#64 |
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.15-amd64-aws-opentelemetry-e2e-tests |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.16-amd64-aws-ipi-shared-vpc-phz-sts-opentelemetry-e2e-tests pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.14-amd64-gcp-ipi-ovn-ipsec-opentelemetry-e2e-tests pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-upgrade-ocp-4.17-amd64-azure-opentelemetry-operator-upgrade pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.13-amd64-aws-ipi-ovn-hypershift-opentelemetry-e2e-tests |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-upgrade-ocp-4.17-amd64-azure-opentelemetry-operator-upgrade pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.14-amd64-gcp-ipi-ovn-ipsec-opentelemetry-e2e-tests |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse ack |
@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: IshwarKanse, vprashar2929 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@IshwarKanse: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
No description provided.