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

IpVersions/IntegrationTest.AllWorkersAreHandlingLoad/IPv6 is flaky #19807

Closed
RyanTheOptimist opened this issue Feb 3, 2022 · 8 comments
Closed
Assignees
Labels
area/test flakes bug stale stalebot believes this issue/PR has not been touched recently

Comments

@RyanTheOptimist
Copy link
Contributor

I have a PR out which simply changes contents of a .md file. However, it had a failure of IpVersions/IntegrationTest.AllWorkersAreHandlingLoad/IPv6 in macos test. Since this PR did not change any code, I think this must have been a flake.

@RyanTheOptimist
Copy link
Contributor Author

@YaoZengzeng it looks like you may have worked on this test recently. Can you take a look?

@RyanTheOptimist
Copy link
Contributor Author

/assign @YaoZengzeng

@repokitteh-read-only
Copy link

@YaoZengzeng cannot be assigned to this issue.

🐱

Caused by: a #19807 (comment) was created by @RyanTheOptimist.

see: more, trace.

@snowp snowp removed the triage Issue requires triage label Feb 4, 2022
@htuch
Copy link
Member

htuch commented Feb 9, 2022

@wrowe code spelunking indicates you added this test. Reading through the code at https://github.com/envoyproxy/envoy/blame/main/test/integration/integration_test.cc#L163, I'm wondering if the OS scheduler and being unlucky could lead to significant connection imbalance.

@htuch
Copy link
Member

htuch commented Feb 9, 2022

I'm going to disable this test later today if we don't have a reasonable plan to fix as it's continuing to flake.

@KBaichoo
Copy link
Contributor

This is still flaking, see CI runs for the following PRs: 18846, 19894, 19630

Does it make sense to disable this test?

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Mar 17, 2022
@github-actions
Copy link

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test flakes bug stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

5 participants