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

flake in TcpTunnelingIntegrationTest.UpstreamHttpFiltersPauseAndResume #35523

Closed
alyssawilk opened this issue Jul 31, 2024 · 5 comments · Fixed by #35917
Closed

flake in TcpTunnelingIntegrationTest.UpstreamHttpFiltersPauseAndResume #35523

alyssawilk opened this issue Jul 31, 2024 · 5 comments · Fixed by #35917
Assignees

Comments

@alyssawilk
Copy link
Contributor

[ RUN ] IpAndHttpVersions/TcpTunnelingIntegrationTest.UpstreamHttpFiltersPauseAndResume/IPv4_Http3Downstream_HttpUpstreamHttpParserNghttp2NoDeferredProcessingLegacyWithUpstreamHttpFilters
test/integration/tcp_tunneling_integration_test.cc:954: Failure
Value of: tcp_client_->write("hello", true)
Actual: false (Failed to complete write or unexpected disconnect. disconnected_: true bytes_drained: 10 bytes_expected: 10)
Expected: true
Stack trace:
0x5633ea055a44: Envoy::(anonymous namespace)::TcpTunnelingIntegrationTest_UpstreamHttpFiltersPauseAndResume_Test::TestBody()
0x5633edae0f15: testing::internal::HandleSehExceptionsInMethodIfSupported<>()
0x5633edadbcad: testing::internal::HandleExceptionsInMethodIfSupported<>()
0x5633edac2574: testing::Test::Run()
0x5633edac2f97: testing::TestInfo::Run()
... Google Test internal frames ...

@vikaschoudhary16
Copy link
Contributor

@alyssawilk ran following command multiple times:

bazel test  -c dbg  //test/integration:tcp_tunneling_integration_test --config=libc++ --test_filter=*IpAndHttpVersions/TcpTunnelingIntegrationTest.UpstreamHttpFiltersPauseAndResume/IPv4_Http3Downstream_HttpUpstreamHttpParserNghttp2NoDeferredProcessingLegacyWithUpstreamHttpFilters* --notest_keep_going --runs_per_test=100 -t-

Not able to get the test failed even once. Can you please review my command once? Also would appreciate any tips on how I can reproduce this.

@alyssawilk
Copy link
Contributor Author

I'd definitely go up to 2k/4k. it that doesn't get you anywhere you could alwys use the scoped test logger to turn up logging for that test so next it fails CI we have debug info, then you can close it off as "can't repro" :-)

@alyssawilk
Copy link
Contributor Author

@phlax
Copy link
Member

phlax commented Aug 29, 2024

this is still happening pretty frequently

@vikaschoudhary16
Copy link
Contributor

oh, will retry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants