Repository navigation
Fix historical backfill runtime compatibility and deadlines - #1149
Conversation
Benchmark previewAdvisory: changes over 15% are warnings, not merge failures. Positive reference-adjusted change means slower; negative means faster. linuxPerformance overviewNo compatible merged baseline comparisons are available; regression status is unknown. Advisory only. Merged baseline: unavailable. Compatible comparisons: 0/360; unavailable: 360.
Typical change is an equal-weight geometric mean of reference-adjusted XFF/main factors. Negative is faster; positive is slower. These correlated cases are not a significance test. Tested merge macosPerformance overviewNo compatible merged baseline comparisons are available; regression status is unknown. Advisory only. Merged baseline: unavailable. Compatible comparisons: 0/360; unavailable: 360.
Typical change is an equal-weight geometric mean of reference-adjusted XFF/main factors. Negative is faster; positive is slower. These correlated cases are not a significance test. Tested merge |
Historical backfills failed on Linux because the selected LLVM linkers need libraries absent from Ubuntu 26.04, and one macOS content-search command exceeded the fixed 60-second deadline. Use a compatible Linux runner, allow longer commands in recorded backfill contracts, and retry only the platforms that still need results.
AG;DR
bazel test //tools:benchmark_compare_test //tools:benchmark_backfill_test //tools:benchmark_campaign_test //tools:benchmark_recovery_test //tools:benchmark_history_testpassed on macOS; Trunk and repository hooks passed. The Ubuntu 22.04 historical build and longer macOS measurement have not yet completed end to end. No retry campaign was launched from this branch.