Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Flakiness: E2E test of GCPBroker #1394

Closed
capri-xiyue opened this issue Jul 7, 2020 · 3 comments
Closed

Flakiness: E2E test of GCPBroker #1394

capri-xiyue opened this issue Jul 7, 2020 · 3 comments
Assignees
Labels
area/broker area/test-and-release Test infrastructure, tests or release flaky-test kind/bug Something isn't working priority/1 Blocks current release defined by release/* label or blocks current milestone release/2
Milestone

Comments

@capri-xiyue
Copy link
Contributor

capri-xiyue commented Jul 7, 2020

Describe the bug
E2E test related to GCP Broker under WI mode is flaky.
Example:
https://prow.knative.dev/view/gcs/knative-prow/pr-logs/pull/google_knative-gcp/1388/pull-google-knative-gcp-wi-tests/1280550413002608640
Error msg is as follows:
TestGCPBroker: test_gcp_broker.go:59: job: error sending cloudevent: 503 Service Unavailable TestGCPBroker: test_gcp_broker.go:59: dummy event wasn't sent to broker

Expected behavior
E2E test of TestGCPBroker consistently pass.

To Reproduce
Steps to reproduce the behavior.

Knative-GCP release version

Additional context
Add any other context about the problem here such as proposed priority

@capri-xiyue capri-xiyue added kind/bug Something isn't working area/test-and-release Test infrastructure, tests or release area/broker priority/1 Blocks current release defined by release/* label or blocks current milestone labels Jul 7, 2020
@capri-xiyue capri-xiyue changed the title Flakiness: E2E test of TestGCPBroker Flakiness: E2E test of GCPBroker Jul 7, 2020
@akashrv akashrv added this to the Backlog milestone Jul 7, 2020
@grantr
Copy link
Contributor

grantr commented Jul 7, 2020

@grac3gao Do you think this issue will be fixed by your investigation of #1362?

@grac3gao-zz
Copy link
Contributor

grac3gao-zz commented Jul 7, 2020

@grantr That may be the different issues. #1362's error is produced in the fanout Pod, this issue's error is produced in the ingress Pod (we handled unknown encoding in ingress Pod). This issue may be fixed by PR #1358

@grac3gao-zz
Copy link
Contributor

fixed by #1415 and #1444

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/broker area/test-and-release Test infrastructure, tests or release flaky-test kind/bug Something isn't working priority/1 Blocks current release defined by release/* label or blocks current milestone release/2
Projects
None yet
Development

No branches or pull requests

5 participants