-
Notifications
You must be signed in to change notification settings - Fork 600
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
[flaky] test/conformance.TestBrokerV1Beta1DataPlaneConsumer/Replies_are_accepted_and_delivered #3791
Comments
Latest result for this test: Passed 2020-08-31 08:55:16 +0000 UTC: ◻ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ◻ ✔ Older builds
2020-08-19 08:53:30 +0000 UTC: ✖ ✔ ✖ ✔ ✔ ◻ ✔ ✖ ✔ ✔ |
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.
Another panic. I'm focusing on looking at this:
|
After fixing the panic. I now see these failures instead of panics. Digging into those next...
|
My next hunch/guess/whatevs is that we make sure pod is up, but the service is not up yet or endpoints are not there, and hence it's actually not ready. Looking at this next... |
all the failed tests are still connection refused:
|
Reopening issue: this test is flaky |
Refactor the tests to have the test resources setup first, and then just use them in the following tests. Hopefully this increases the stability of the broker tests Realted: knative#3791
Refactor the tests to have the test resources setup first, and then just use them in the following tests. Hopefully this increases the stability of the broker tests Related: knative#3791
Refactor the tests to have the test resources setup first, and then just use them in the following tests. Hopefully this increases the stability of the broker tests Related: #3791
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.
…3885) * Add explicit content encoding to event-senders in broker conf test 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. * Errant rebase, added a bracket
Closing issue: this test has passed in latest 2 scans |
Auto-generated issue tracking flakiness of test
The text was updated successfully, but these errors were encountered: