CI mirror: run flutter shards at concurrency 2

At the default concurrency a shard peaked at 3.9 GiB and was
OOM-killed inside capped.sh's 2 GiB scope; at 4 it still hit the
limit now and then. At 2 a shard peaks at 1.8 GiB, about 22 s.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Krzysztof Rudnicki 2026-11-21 18:20:04 +01:00
parent e942404213
commit 70c5d034a8
2 changed files with 7 additions and 3 deletions

View File

@ -2,7 +2,7 @@ name: diet_guard_app
description: "Companion phone app for diet_guard: log meals on the go."
publish_to: 'none'
version: 1.0.190+1
version: 1.0.192+1
environment:
sdk: ^3.12.2

View File

@ -167,9 +167,13 @@ run_flutter_test_shard() {
# A private TMPDIR per shard: on the shared /tmp a shard stalled at ~2 s of
# CPU for 15+ minutes (2026-11-21, held a build slot past 60 s) while the
# same shard with its own TMPDIR finished in well under a minute.
local tmp status=0
# Two test isolates, not flutter's default of one per spare core: at the
# default a shard peaked at 3.9 GiB and was OOM-killed inside capped.sh's
# 2 GiB scope; at 4 it still hit 2 GiB and was killed now and then; at 2
# it peaks at 1.8 GiB and runs in ~22 s (2026-11-21).
local tmp status=0 concurrency=${FLUTTER_TEST_CONCURRENCY:-2}
tmp="$(mktemp -d "${XDG_CACHE_HOME:-$HOME/.cache}/diet-guard-flutter-test.XXXXXX")"
(cd "$APP_DIR" && TMPDIR="$tmp" flutter_clean_env test "${files[@]}") || status=$?
(cd "$APP_DIR" && TMPDIR="$tmp" flutter_clean_env test --concurrency="$concurrency" "${files[@]}") || status=$?
rm -rf -- "$tmp"
((status == 0)) || fail "flutter test shard $index/$total"
}