-
Notifications
You must be signed in to change notification settings - Fork 387
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
BenchmarkExportConntrackConns panics #2984
Comments
I'll look into it. |
The Go benchmark test workflow has recorded the benchmark error of #2854 : https://github.com/antrea-io/antrea/actions/runs/1423364727 We can avoid this if we run the Go benchmark workflow for each PR, it will take about 17minutes which run the benchmarks twice. I think we can add a step in go.yaml to run the benchmarks, it will only take about 9-10minutes. |
@wenqiq 10 minutes is still pretty large when run every time the PR is updated. |
Run the benchmarks once for each PR. Fixes antrea-io#2984 Signed-off-by: Wenqi Qiu <wenqiq@vmware.com>
Run the benchmarks once for each PR. Fixes antrea-io#2984 Signed-off-by: Wenqi Qiu <wenqiq@vmware.com>
Run the benchmarks once for each PR. Fixes antrea-io#2984 Signed-off-by: Wenqi Qiu <wenqiq@vmware.com>
Run the benchmarks once for each PR. Fixes antrea-io#2984 Signed-off-by: Wenqi Qiu <wenqiq@vmware.com>
Run the benchmarks once for each PR. Fixes #2984 Signed-off-by: Wenqi Qiu <wenqiq@vmware.com>
Run the benchmarks once for each PR. Fixes antrea-io#2984 Signed-off-by: Wenqi Qiu <wenqiq@vmware.com>
Describe the bug
BenchmarkExportConntrackConns
is panicking after merging #2854.This is causing the
Go Benchmark Test
workflow to fail on the main branch.The text was updated successfully, but these errors were encountered: