Skip to content

Change signed mulitply to unsigned

conbench-apache-arrow / Conbench performance report required action Jan 9, 2025 in 0s

Some benchmarks had errors

Thanks for your patience. Conbench analyzed the 3 benchmarking runs that have been run so far on PR commit 4462ceb.

Benchmarks with errors

These are errors that were caught while running the benchmarks. You can click each link to go to the Conbench entry for that benchmark, which might have more information about what the error was.

Benchmarks with performance regressions

There weren't enough matching historic runs in Conbench to make a call on whether there were regressions or not.

To use the lookback z-score method of determining regressions, there need to be at least two historic runs on the default branch which, when compared to one of the runs on the contender commit, are on the same hardware, and have at least one of the same benchmark case and context pairs.

All benchmark runs analyzed:

View more details on conbench-apache-arrow