Skip to content
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

[release-1.7] Properly export trace for duplicated "finished" event #62

Merged

Conversation

matzew
Copy link
Member

@matzew matzew commented Dec 23, 2022

Backport of upstream knative#6540

…native#6540)

* Properly export trace for duplicated "finished" event

Fixes an issue with duplicated finished event in which case the
following error was thrown:
knative.dev/eventing/test/upgrade/prober.(*prober).getStepNoFromMsg
...
panic: runtime error: index out of range [1] with length 0

* Define FinishedEventPrefix and reuse it

Co-authored-by: Martin Gencur <mgencur@redhat.com>
@openshift-ci openshift-ci bot requested review from lberk and pierDipi December 23, 2022 12:57
@matzew
Copy link
Member Author

matzew commented Dec 23, 2022

/cherry-pick release-v1.8

@openshift-cherrypick-robot

@matzew: once the present PR merges, I will cherry-pick it on top of release-v1.8 in a new PR and assign it to you.

In response to this:

/cherry-pick release-v1.8

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/test-infra repository.

Copy link

@aliok aliok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci
Copy link

openshift-ci bot commented Dec 23, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, matzew

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 0ce4796 into openshift-knative:release-v1.7 Dec 23, 2022
@openshift-cherrypick-robot

@matzew: new pull request could not be created: failed to create pull request against openshift-knative/eventing#release-v1.8 from head openshift-cherrypick-robot:cherry-pick-62-to-release-v1.8: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift-knative:release-v1.8 and openshift-cherrypick-robot:cherry-pick-62-to-release-v1.8"}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"}

In response to this:

/cherry-pick release-v1.8

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/test-infra repository.

@aliok
Copy link

aliok commented Dec 26, 2022

@matzew I think you need to check this manually when you're back. I mean, why the cherry pick fails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants