From f1fb5e4e7a5fac6a237d6e30891c6069844e2e7c Mon Sep 17 00:00:00 2001 From: discord9 Date: Thu, 15 Oct 2026 11:17:18 +0000 Subject: [PATCH] ci(coverage): set RUST_MIN_STACK=8MB in merge_group coverage job (#9615) The merge_group coverage job did not set RUST_MIN_STACK, so test threads ran with the default 2MiB stack while the regular test job (and the production runtime in debug) use 8MiB. The deeper PromQL planning chain from #9494 overflows 2MiB under llvm-cov instrumentation, aborting tests::promql_test::anon_promql_ratio_repro::case_1_test_with_standalone with SIGABRT (12/12 failures across three merge-queue candidates). Align the coverage job with the existing 8MiB test policy. Signed-off-by: discord9 (cherry picked from commit 60097a062872f0fe5cfbc8341c4c600d824476c7) --- .github/workflows/rust.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml index e29b69678c1..e9c77554e07 100644 --- a/.github/workflows/rust.yml +++ b/.github/workflows/rust.yml @@ -294,6 +294,7 @@ jobs: env: CARGO_BUILD_RUSTFLAGS: "-C link-arg=-fuse-ld=mold" RUST_BACKTRACE: 1 + RUST_MIN_STACK: 8388608 # 8MB, aligned with the test job CARGO_INCREMENTAL: 0 # Runs the object-store matrix against the local MinIO from # tests-integration/fixtures. Real AWS S3 is covered by the nightly