Deflake app test suite: hermetic caches, robust async waits, perf-gate retry (#1365)

Four spurious CI failures on July 5, all loaded-runner flakiness:

- ViewSmokeTests.voiceAndMediaViews_renderAndWarmCaches asserted an exact
  bin count on WaveformCache.shared for the same URL the mounted
  VoiceNoteView was concurrently warming at its default 120-bin width;
  whichever barrier write landed last owned the entry. Probe the cache with
  a dedicated audio file no view touches, and purge both URLs. Also replace
  the fixed 250ms sleep for loadDuration's background hop with a waitUntil
  poll.

- sendImage_privateChatProcessesAndTransfersImage (and its sendVoiceNote /
  sendImage siblings) wait on work that hops through Task.detached; the
  global executor is shared with every parallel test worker, so a loaded
  runner can exceed the 5s wait. Raise those positive waits to
  TestConstants.longTimeout (10s) — waitUntil returns as soon as the
  condition holds, so passing runs are unaffected.

- subscribeNostrEvent_addsToTimeline_ifMatchesGeohash raced concurrently
  running suites (e.g. CommandProcessorTests) on the process-wide
  LocationChannelManager singleton: a mid-test channel flip reroutes or
  drops the event permanently, so no fixed wait recovers. The wait loop now
  re-asserts the channel and redelivers the event on each poll — idempotent
  because channel switches clear the processed-event set and the store
  dedups by message ID — so interference heals while genuine failures still
  time out.

- The performance floor gate failed on a saturated runner
  (gcs.buildAndDecode at 85% of floor). check-perf-floors.sh now re-runs
  the benchmark suite up to twice when a metric lands below floor,
  appending to the same PERF log and keeping each benchmark's best value
  across attempts: noise clears on a retry, a real algorithmic regression
  fails every attempt. Floors are unchanged and never lowered by the
  mechanism; missing-benchmark failures exit immediately without retrying.

Co-authored-by: jack <jackjackbits@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
jack
2026-07-06 10:25:17 +02:00
committed by GitHub
co-authored by jack Claude Fable 5
parent c74e212ea3
commit 8296630cf3
5 changed files with 139 additions and 24 deletions
+86 -13
View File
@@ -11,16 +11,34 @@
# never runner variance. Raise floors deliberately after intentional
# improvements; never tune them to chase noise.
#
# Retry-on-noise: even generous floors can be dipped under by a saturated
# runner (observed: gcs.buildAndDecode at 85% of floor on a loaded GitHub
# macOS runner). When a benchmark lands below its floor, the gate re-runs the
# benchmark suite — appending to the same PERF log — and keeps each
# benchmark's BEST observed value across attempts. Runner noise clears on a
# retry; a real algorithmic regression stays below floor on every attempt and
# still fails. Floors themselves are never lowered by this mechanism.
#
# Usage: scripts/check-perf-floors.sh <test-output-file> [floors-file]
#
# Environment:
# BITCHAT_PERF_GATE_ATTEMPTS total measurement attempts (default 3)
# BITCHAT_PERF_REMEASURE_CMD command run to re-measure on a below-floor
# result (default: swift test --quiet
# --filter PerformanceBaselineTests). The
# command runs with BITCHAT_PERF_LOG pointed at
# the output file so new PERF lines append.
#
# Skips gracefully (exit 0) when:
# - BITCHAT_SKIP_PERF_BASELINES=1 (perf tests were skipped), or
# - the output contains no PERF lines (e.g. package-only matrix entries).
#
# Fails (exit 1) when:
# - any benchmark reports throughput below its floor, or
# - PERF lines are present but a floored benchmark is missing
# (a silently-dropped benchmark must be an explicit floors-file change).
# Fails when:
# - any benchmark reports throughput below its floor on every attempt
# (exit 1), or
# - PERF lines are present but a floored benchmark is missing — a
# silently-dropped benchmark must be an explicit floors-file change and
# is not retried (exit 3).
set -euo pipefail
@@ -31,6 +49,8 @@ fi
OUTPUT_FILE="$1"
FLOORS_FILE="${2:-$(cd "$(dirname "$0")/.." && pwd)/bitchatTests/Performance/perf-floors.json}"
MAX_ATTEMPTS="${BITCHAT_PERF_GATE_ATTEMPTS:-3}"
REMEASURE_CMD="${BITCHAT_PERF_REMEASURE_CMD:-swift test --quiet --filter PerformanceBaselineTests}"
if [[ "${BITCHAT_SKIP_PERF_BASELINES:-}" == "1" ]]; then
echo "perf-floors: BITCHAT_SKIP_PERF_BASELINES=1 — skipping gate."
@@ -52,7 +72,17 @@ if ! grep -q 'PERF\[' "$OUTPUT_FILE"; then
exit 0
fi
OUTPUT_FILE="$OUTPUT_FILE" FLOORS_FILE="$FLOORS_FILE" python3 - <<'PYEOF'
# Absolute path so re-measurement appends to the same file regardless of the
# working directory the test process runs in.
case "$OUTPUT_FILE" in
/*) ;;
*) OUTPUT_FILE="$(pwd)/$OUTPUT_FILE" ;;
esac
# Exit codes: 0 = all floors met, 1 = below floor (retryable — noise vs
# regression undecided), 3 = floored benchmark missing (not retryable).
check_floors() {
OUTPUT_FILE="$OUTPUT_FILE" FLOORS_FILE="$FLOORS_FILE" python3 - <<'PYEOF'
import json
import os
import re
@@ -72,15 +102,20 @@ with open(output_file, errors="replace") as f:
for line in f:
m = pattern.search(line)
if m:
# Keep the last reported value if a benchmark prints twice.
measured[m.group(1)] = (float(m.group(2)), m.group(3))
# Keep the BEST reported value: measurement retries append to the
# same log, and a healthy benchmark only needs to clear its floor
# once — a real regression never does.
name, value, unit = m.group(1), float(m.group(2)), m.group(3)
if name not in measured or value > measured[name][0]:
measured[name] = (value, unit)
failures = []
below_floor = []
missing = []
print(f"perf-floors: checking {len(measured)} benchmark(s) against {len(floors)} floor(s)")
for name in sorted(set(floors) | set(measured)):
floor = floors.get(name)
if name not in measured:
failures.append(
missing.append(
f" MISSING {name}: floored benchmark reported no PERF line "
f"(removed/renamed? update perf-floors.json in the same change)")
continue
@@ -92,13 +127,18 @@ for name in sorted(set(floors) | set(measured)):
line = f" {status:8} {name}: {value:.0f} {unit}/sec (floor {floor})"
print(line)
if value < floor:
failures.append(
below_floor.append(
f" BELOW {name}: {value:.0f} {unit}/sec is under floor {floor} "
f"({value / floor * 100:.0f}% of floor)")
if failures:
print("\nperf-floors: FAILED — order-of-magnitude-class regression suspected:")
print("\n".join(failures))
if missing:
print("\nperf-floors: FAILED — floored benchmark(s) missing from the output:")
print("\n".join(missing + below_floor))
sys.exit(3)
if below_floor:
print("\nperf-floors: below floor — order-of-magnitude-class regression suspected:")
print("\n".join(below_floor))
print("\nFloors are ~25% of healthy local throughput; falling below one means an")
print("algorithmic regression, not runner noise. If the change is intentional,")
print("update bitchatTests/Performance/perf-floors.json deliberately.")
@@ -106,3 +146,36 @@ if failures:
print("perf-floors: all benchmarks at or above their floors.")
PYEOF
}
attempt=1
while true; do
gate_status=0
check_floors || gate_status=$?
case "$gate_status" in
0)
exit 0
;;
1)
# Below floor: retry to separate runner noise from regression.
;;
*)
# Missing benchmark or parse/setup error: re-measuring can't help.
exit "$gate_status"
;;
esac
if (( attempt >= MAX_ATTEMPTS )); then
echo "perf-floors: still below floor after $attempt measurement attempt(s) — treating as a real regression." >&2
exit 1
fi
attempt=$((attempt + 1))
echo "perf-floors: re-measuring (attempt $attempt of $MAX_ATTEMPTS) to separate runner noise from a real regression."
# Word splitting of REMEASURE_CMD is deliberate: it is a command line.
if ! BITCHAT_PERF_LOG="$OUTPUT_FILE" $REMEASURE_CMD; then
echo "perf-floors: re-measurement command failed: $REMEASURE_CMD" >&2
exit 1
fi
done