-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Benchmarking][CI] Benchmarking buildkite runs fail to build Arrow #45939
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
Comments
These failures can be seen here: |
There was a new release of Google Benchmark yesterday (1.9.2) which is the one used on the run and checks with the problem: |
It does seem related to this change: But I am unsure on the fix, @pitrou any idea? |
I think this might be because the benchmark function names ( |
Benchmarks fail compiling with Google Benchmark 1.9.2. This is because the benchmark function names conflict with Arrow API function names. We don't want to break continuous benchmarking history by changing the benchmark names, so instead move the benchmarks to a dedicated namespace.
Benchmarks fail compiling with Google Benchmark 1.9.2. This is because the benchmark function names conflict with Arrow API function names. We don't want to break continuous benchmarking history by changing the benchmark names, so instead move the benchmarks to a dedicated namespace.
Benchmarks fail compiling with Google Benchmark 1.9.2. This is because the benchmark function names conflict with Arrow API function names. We don't want to break continuous benchmarking history by changing the benchmark names, so instead move the benchmarks to a dedicated namespace.
Benchmarks fail compiling with Google Benchmark 1.9.2. This is because the benchmark function names conflict with Arrow API function names. We don't want to break continuous benchmarking history by changing the benchmark names, so instead move the benchmarks to a dedicated namespace.
Benchmarks fail compiling with Google Benchmark 1.9.2. This is because the benchmark function names conflict with Arrow API function names. We don't want to break continuous benchmarking history by changing the benchmark names, so instead move the benchmarks to a dedicated namespace.
### Rationale for this change Benchmarks fail compiling with Google Benchmark 1.9.2. The errors seem triggered by this change upstream: google/benchmark#1948 ### What changes are included in this PR? * Move some benchmark functions to a dedicated namespace so that there is no ambiguity with other functions * Reduce reliance on templating in benchmark functions to avoid resolution ambiguities * Other required fixes Note that we don't rename the benchmark functions, to avoid breaking continuous benchmarking history. ### Are these changes tested? By continuous benchmarking. ### Are there any user-facing changes? No. * GitHub Issue: #45939 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Issue resolved by pull request 45942 |
…45942) ### Rationale for this change Benchmarks fail compiling with Google Benchmark 1.9.2. The errors seem triggered by this change upstream: google/benchmark#1948 ### What changes are included in this PR? * Move some benchmark functions to a dedicated namespace so that there is no ambiguity with other functions * Reduce reliance on templating in benchmark functions to avoid resolution ambiguities * Other required fixes Note that we don't rename the benchmark functions, to avoid breaking continuous benchmarking history. ### Are these changes tested? By continuous benchmarking. ### Are there any user-facing changes? No. * GitHub Issue: apache#45939 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
…45942) ### Rationale for this change Benchmarks fail compiling with Google Benchmark 1.9.2. The errors seem triggered by this change upstream: google/benchmark#1948 ### What changes are included in this PR? * Move some benchmark functions to a dedicated namespace so that there is no ambiguity with other functions * Reduce reliance on templating in benchmark functions to avoid resolution ambiguities * Other required fixes Note that we don't rename the benchmark functions, to avoid breaking continuous benchmarking history. ### Are these changes tested? By continuous benchmarking. ### Are there any user-facing changes? No. * GitHub Issue: apache#45939 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
As noted by @zanmato1984 on this PR:
Benchmarks have stopped running. The latest benchmarked commit PR merged is:
#45929
The next one merged doesn't seem to have benchmarks run:
#45907
Which matches with the runs here:
https://conbench.ursa.dev/
It does seem that buildkite runs are failing with the following error:
Component(s)
Benchmarking
The text was updated successfully, but these errors were encountered: