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 #6540

Conversation

knative-prow-robot
Copy link
Contributor

This is an automated cherry-pick of #6536


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
@knative-prow knative-prow bot added area/test-and-release Test infrastructure, tests or release size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 23, 2022
@codecov
Copy link

codecov bot commented Sep 23, 2022

Codecov Report

Base: 81.96% // Head: 81.96% // No change to project coverage 👍

Coverage data is based on head (a164026) compared to base (9967e86).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff              @@
##           release-1.7    #6540   +/-   ##
============================================
  Coverage        81.96%   81.96%           
============================================
  Files              235      235           
  Lines            11726    11726           
============================================
  Hits              9611     9611           
  Misses            1644     1644           
  Partials           471      471           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Member

@matzew matzew 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

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Sep 26, 2022
@knative-prow
Copy link

knative-prow bot commented Sep 26, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knative-prow-robot, 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

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 26, 2022
@knative-prow knative-prow bot merged commit 0bf545a into knative:release-1.7 Sep 26, 2022
matzew pushed a commit to matzew/eventing that referenced this pull request Dec 23, 2022
…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-merge-robot pushed a commit to openshift-knative/eventing that referenced this pull request Dec 23, 2022
…native#6540) (#62)

* 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>

Co-authored-by: Knative Prow Robot <knative-prow-robot@google.com>
Co-authored-by: Martin Gencur <mgencur@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test-and-release Test infrastructure, tests or release lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants