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

http: rolling back the dispatcher cleanup #9244

Merged
merged 1 commit into from
Dec 8, 2019

Conversation

alyssawilk
Copy link
Contributor

Alas, the test wasn't testing what it looked like it was testing, and fails when it is fixed.
I believe we need the extra dispatch there due to the order of readDisables.

Risk Level: low
Testing: new integration test
Docs Changes: n/a
Release Notes: n/a

mattklein123
mattklein123 previously approved these changes Dec 5, 2019
@alyssawilk
Copy link
Contributor Author

tl;dr Pipeline test was checking for two different response codes, so got 2 responses
PipelineInline was checking for the same response code and looked at one response twice.
sigh.
Anyway, fixing the test stalls, which surprises me - I thought that the kick in the other PR would save us the need to redispatch, but integration tests prove otherwise.

@mattklein123
Copy link
Member

Needs a DCO fix. :(

/wait

This reverts commit 281243e.

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@mattklein123 mattklein123 merged commit 6cc4f95 into envoyproxy:master Dec 8, 2019
@alyssawilk alyssawilk deleted the rollback branch May 18, 2020 14:22
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