From 910c22b6053d3df814dff6d84679e69a9116eab8 Mon Sep 17 00:00:00 2001 From: Andrii Baranov Date: Thu, 6 Aug 2026 11:21:19 -0700 Subject: [PATCH 1/2] ci(profile): stop regenerating committed schedules --- .github/workflows/profile-bench.yml | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/.github/workflows/profile-bench.yml b/.github/workflows/profile-bench.yml index 5fa927e85..52bb92c9c 100644 --- a/.github/workflows/profile-bench.yml +++ b/.github/workflows/profile-bench.yml @@ -190,9 +190,6 @@ jobs: - name: Verify profile-ci feature coverage run: ./scripts/check_profile_ci_features.sh - - name: Generate schedule tables - run: scripts/generate-schedule-tables.sh - - name: Build merge-base profile binary if: github.event_name == 'pull_request' && env.AKITA_BENCH_BASELINE_MODES_OK == '1' env: @@ -206,9 +203,10 @@ jobs: fi ( cd "$RUNNER_TEMP/bench-base" && - if [ -x ./scripts/generate-schedule-tables.sh ]; then - ./scripts/generate-schedule-tables.sh - fi + # Profile benchmarks consume the generated tables committed at + # each revision. Schedule-generation drift is enforced by the + # dedicated CI guard, so regenerating here only warms unrelated + # build artifacts and delays every matrix cell. if python3 scripts/cargo_feature_exists.py akita-pcs profile-ci; then CARGO_TARGET_DIR="$RUNNER_TEMP/bench-base-target" \ cargo build --release --quiet --example profile \ From 694d3fa53b38e47269238e70a0eba7fa89d85449 Mon Sep 17 00:00:00 2001 From: Andrii Baranov Date: Thu, 6 Aug 2026 17:07:33 -0700 Subject: [PATCH 2/2] ci: retrigger checks after GitHub outage