Skip to content

test: fixing timeout#20468

Merged
alyssawilk merged 1 commit intoenvoyproxy:mainfrom
alyssawilk:timeout
Mar 22, 2022
Merged

test: fixing timeout#20468
alyssawilk merged 1 commit intoenvoyproxy:mainfrom
alyssawilk:timeout

Conversation

@alyssawilk
Copy link
Copy Markdown
Contributor

we had a connect test which was doing sendRawHttpAndWaitForResponse, which generally waits for a completely framed response, and the while point of CONNECT proxying is the "body" isn't ever complete. Setting disconnect_after_headers_complete = true means the test finishes up after the headers are sent rather than waiting for a body which will never arrive.

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

Nice thanks!

@alyssawilk alyssawilk enabled auto-merge (squash) March 22, 2022 20:45
@alyssawilk alyssawilk merged commit 14f597b into envoyproxy:main Mar 22, 2022
alyssawilk added a commit that referenced this pull request Mar 30, 2022
…#20488)

Follow up on #20468 to future-proof against slow tests, by adding a default timeout to the raw connection driver
This caught a whole bunch of tests which were waiting 15s for delay close.

Risk Level: n/a (test only)
Testing: CI

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
ravenblackx pushed a commit to ravenblackx/envoy that referenced this pull request Jun 8, 2022
we had a connect test which was doing sendRawHttpAndWaitForResponse, which generally waits for a completely framed response, and the while point of CONNECT proxying is the "body" isn't ever complete. Setting disconnect_after_headers_complete = true means the test finishes up after the headers are sent rather than waiting for a body which will never arrive.

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
ravenblackx pushed a commit to ravenblackx/envoy that referenced this pull request Jun 8, 2022
…envoyproxy#20488)

Follow up on envoyproxy#20468 to future-proof against slow tests, by adding a default timeout to the raw connection driver
This caught a whole bunch of tests which were waiting 15s for delay close.

Risk Level: n/a (test only)
Testing: CI

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@alyssawilk alyssawilk deleted the timeout branch August 4, 2022 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants