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

Flaky traceflow e2e test intraNodeICMPSrcIPDroppedTraceflowIPv4 #5609

Closed
luolanzone opened this issue Oct 24, 2023 · 1 comment · Fixed by #5954
Closed

Flaky traceflow e2e test intraNodeICMPSrcIPDroppedTraceflowIPv4 #5609

luolanzone opened this issue Oct 24, 2023 · 1 comment · Fixed by #5954
Assignees

Comments

@luolanzone
Copy link
Contributor

TestTraceflow in e2e tests framework failed often. Here is a report from @antoninbas 's data collection. https://github.com/antoninbas/antrea-flaky-tests/blob/main/results/2023_10_23/results-90.txt

In the past 90 days, the sub test intraNodeICMPSrcIPDroppedTraceflowIPv4 failed 5 times, we may need investigate it's a code issue or test issue, therefore, we can reduce the rerun efforts and improve test efficiency.

@luolanzone luolanzone added this to the Antrea v1.15 release milestone Oct 31, 2023
@luolanzone luolanzone removed this from the Antrea v1.15 release milestone Jan 3, 2024
@hangyan
Copy link
Member

hangyan commented Jan 31, 2024

cross posting here. #5760

The most frequently happend case is intraNodeICMPDstIPTraceflowIPv4 now. (example: https://github.com/antrea-io/antrea/actions/runs/7636346955/job/20803790694?pr=5909). It's caused by timeout failure and didn't have a direct cause. Logs didn't show any clues yet, i'm planning to add more debug output to help narrow down the scope.

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 a pull request may close this issue.

2 participants