From 63a14a68baf4a3c23d5f4583a89f534abf09ace3 Mon Sep 17 00:00:00 2001 From: Hubert Gruszecki Date: Fri, 29 May 2026 09:10:24 +0200 Subject: [PATCH] ci(connectors): raise vm.max_map_count for Doris in coverage job The Doris connector sink (#3215) added the sysctl bump only to the pre-merge action, so the coverage-baseline job kept the runner default of 262144. Doris 4.0.3's start_be.sh hard-exits below 2000000, making the fixture preflight panic and failing all Doris sink integration tests post-merge. Mirror the same host-only sysctl step before the test run so the coverage job follows the identical container-boot path. --- .github/workflows/coverage-baseline.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.github/workflows/coverage-baseline.yml b/.github/workflows/coverage-baseline.yml index 95dc655bef..958b242225 100644 --- a/.github/workflows/coverage-baseline.yml +++ b/.github/workflows/coverage-baseline.yml @@ -60,6 +60,14 @@ jobs: with: tool: cargo-llvm-cov + # Doris 4.0.3's start_be.sh hard-`exit 1`s unless vm.max_map_count >= 2000000. + # Host-only kernel param (no container can raise it). Mirrors the same step in + # .github/actions/rust/pre-merge/action.yml; without it every Doris connector + # integration test panics at fixture setup. + - name: Raise vm.max_map_count for Doris + run: sudo sysctl -w vm.max_map_count=2000000 || true + shell: bash + - name: Build and test with coverage run: | source <(cargo llvm-cov show-env --export-prefix)