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

Fix flaky closePipelinedAfterTwoRequestsSentBeforeAnyResponseReceived #1557

Merged

Conversation

idelpivnitskiy
Copy link
Member

Motivation:

closePipelinedAfterTwoRequestsSentBeforeAnyResponseReceived may be in
a situation when the 2nd request actually gets written after client
receives GO_AWAY frame from the server. Therefore, Http2Exception is
also excepted. We will use IOException for simplicity and consistency.

Modifications:

  • assertClosedChannelException should expect either
    ClosedChannelException or IOException;

Result:

closePipelinedAfterTwoRequestsSentBeforeAnyResponseReceived is not
flaky.

Motivation:

`closePipelinedAfterTwoRequestsSentBeforeAnyResponseReceived` may be in
a situation when the 2nd request actually gets written after client
receives `GO_AWAY` frame from the server. Therefore, `Http2Exception` is
also excepted. We will use `IOException` for simplicity and consistency.

Modifications:

- `assertClosedChannelException` should expect either
`ClosedChannelException` or `IOException`;

Result:

`closePipelinedAfterTwoRequestsSentBeforeAnyResponseReceived` is not
flaky.
@idelpivnitskiy idelpivnitskiy requested a review from bondolo May 12, 2021 23:46
@idelpivnitskiy idelpivnitskiy merged commit 8d92bb5 into apple:main May 17, 2021
@idelpivnitskiy idelpivnitskiy deleted the assertClosedChannelException branch May 17, 2021 18:06
hbelmiro pushed a commit to hbelmiro/servicetalk that referenced this pull request May 23, 2021
…d` (apple#1557)

Motivation:

`closePipelinedAfterTwoRequestsSentBeforeAnyResponseReceived` may be in
a situation when the 2nd request actually gets written after client
receives `GO_AWAY` frame from the server. Therefore, `Http2Exception` is
also excepted. We will use `IOException` for simplicity and consistency.

Modifications:

- `assertClosedChannelException` should expect either
`ClosedChannelException` or `IOException`;

Result:

`closePipelinedAfterTwoRequestsSentBeforeAnyResponseReceived` is not
flaky.
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