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

TestTraceflow/testTraceflowIntraNode/traceflowGroupTest failed frequently #5760

Closed
tnqn opened this issue Nov 30, 2023 · 4 comments · Fixed by #5954
Closed

TestTraceflow/testTraceflowIntraNode/traceflowGroupTest failed frequently #5760

tnqn opened this issue Nov 30, 2023 · 4 comments · Fixed by #5954
Assignees
Labels
area/test/e2e Issues or PRs related to Antrea specific end-to-end testing. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test.

Comments

@tnqn tnqn added area/test/e2e Issues or PRs related to Antrea specific end-to-end testing. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. labels Nov 30, 2023
@tnqn
Copy link
Member Author

tnqn commented Nov 30, 2023

@gran-vmv @luolanzone

@hangyan
Copy link
Member

hangyan commented Jan 31, 2024

Progress:
case 1 / packet header mismatch: added detailed log output, waiting for more occurrence.
case 2 / timeout: no findings yet, antrea logs didn't show any errors / clues, considering adding more log to identidy the specific test object.

@tnqn
Copy link
Member Author

tnqn commented Feb 1, 2024

The flake has been happening for months and caused many reruns, and I'm concerned it may mean users could also encounter the timeout when they already meet a real connectivity issue and try to debug using Traceflow, which would cause a pretty bad impression. I could help take a look if the problem is unclear yet.

@hangyan
Copy link
Member

hangyan commented Feb 1, 2024

The flake has been happening for months and caused many reruns, and I'm concerned it may mean users could also encounter the timeout when they already meet a real connectivity issue and try to debug using Traceflow, which would cause a pretty bad impression. I could help take a look if the problem is unclear yet.

Sure thanks. I have examined the related logs(2 cases before) but it shows that all the test traceflow objects has been reconcile successfully, in a short time period. I was planning to also print the specific traceflow name in tests code to help narrow down the scope in the following occurrences. (#5953 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test/e2e Issues or PRs related to Antrea specific end-to-end testing. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants