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

Add explicit content encoding to event-senders in broker conf test #3885

Merged

Conversation

lberk
Copy link
Member

@lberk lberk commented Aug 19, 2020

Realted: #3791

For broker data plane conformance tests, when observing some of the
errors in pod sender logs, the following message was seen:

"Got response from http://broker-ingress.knative-eventing-28b9ei2f23.svc.cluster.local/test-broker-v1-beta1-data-plane-consumer-wzjjv/br
failed to convert response into event: unknown Message encoding"

Add a sender.WithEncoding(ce.EncodingStructured) option to the event
sender in an attempt to make the conformance tests more robust.


Make broker conformance tests more robust

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Aug 19, 2020
@knative-prow-robot knative-prow-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 19, 2020
@knative-prow-robot knative-prow-robot added the area/test-and-release Test infrastructure, tests or release label Aug 19, 2020
@matzew
Copy link
Member

matzew commented Aug 20, 2020

/test pull-knative-eventing-unit-tests

Copy link
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

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

We got the same error message:

2020/08/19 20:10:01 Got response from http://broker-ingress.knative-eventing-pxo9jvqv7n.svc.cluster.local/test-broker-v1-beta1-data-plane-ingress-5gf5g/br
failed to convert response into event: unknown Message encoding

Such error message comes from the event-sender (https://github.com/knative/eventing/blob/master/test/test_images/event-sender/main.go#L158), and I think it's expected.

@lberk
Copy link
Member Author

lberk commented Aug 20, 2020

/retest

@vaikas
Copy link
Contributor

vaikas commented Aug 20, 2020

It's just noise, but we should probably clean this up indeed.
/lgtm
/approve

@grantr
Copy link
Contributor

grantr commented Aug 20, 2020

Why didn't @vaikas approval work...
/woof
/lgtm
/approve

@albertomilan
Copy link

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 20, 2020
@grantr
Copy link
Contributor

grantr commented Aug 20, 2020

/approve

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 20, 2020
@vaikas
Copy link
Contributor

vaikas commented Aug 27, 2020

@lberk looks like this doesn't have the 'wait for service endpoint' (based on the test failure), mind rebasing?

@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 27, 2020
Realted: knative#3791

For broker data plane conformance tests, when observing some of the
errors in pod sender logs, the following message was seen:

"Got response from http://broker-ingress.knative-eventing-28b9ei2f23.svc.cluster.local/test-broker-v1-beta1-data-plane-consumer-wzjjv/br
failed to convert response into event: unknown Message encoding"

Add a `sender.WithEncoding(ce.EncodingStructured)` option to the event
sender in an attempt to make the conformance tests more robust.
@lberk lberk force-pushed the robustify-broker-dataplane-tests branch from 7fc23fc to 8cfd160 Compare August 27, 2020 19:54
@knative-prow-robot knative-prow-robot removed lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 27, 2020
@lberk
Copy link
Member Author

lberk commented Aug 27, 2020

@vaikas done

@knative-test-reporter-robot

The following jobs failed:

Test name Triggers Retries
pull-knative-eventing-conformance-tests 0/3

Failed non-flaky tests preventing automatic retry of pull-knative-eventing-conformance-tests:

_go_tests.GoTests

@vaikas
Copy link
Contributor

vaikas commented Aug 27, 2020

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grantr, lberk, vaikas

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-robot knative-prow-robot merged commit c00bf15 into knative:master Aug 27, 2020
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 cla: yes Indicates the PR's author has signed the CLA. 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.

9 participants