Skip to content

"Wait" is overly used in e2e/conformance #1178

@mattmoor

Description

@mattmoor

The conformance (and possibly e2e) tests have a number of checks that poll for success. This masks problems where we say we're Ready but aren't actually.

We should change the e2e test to use Wait methods a bit more sparingly and then concretely check the state of the system.

If this is too flaky, we can consider adding retries, but the idea of "Wait" feels wrong to me.

/assign @mattmoor

I'll see how flaky this is after we get it re-enabled with Wait in place.

Metadata

Metadata

Assignees

Labels

area/test-and-releaseIt flags unit/e2e/conformance/perf test issues for product featuresgood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.kind/specDiscussion of how a feature should be exposed to customers.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIssues which should be fixed (post-triage)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions