mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-07-09 16:00:59 +00:00
201819f8f8
A full local go test run on 2026-06-11 failed pkg/metrics while vite builds were saturating the machine. Reproduced under synthetic 8-core load: only the TestSLO_* wall-clock p95 assertions failed, never the functional tests. A latency budget measured on a shared dev machine cannot distinguish host contention from a code regression; load storms inflated medians up to ~4x with no code change, so no absolute threshold separates the two. Route the latency SLO assertions (pkg/metrics, internal/api, internal/monitoring) and the load/stress perf assertions (internal/api) through helpers that keep strict enforcement on GitHub Actions runners (controlled environment, existing hosted-runner envelopes unchanged) and skip locally on overrun, printing the full p50/p95/p99 distribution in the skip message. A local pass still means the budget was genuinely met. Error-response and correctness checks remain hard failures. CI -race runs are unaffected: these tests already skip under the race detector. Verified: pkg/metrics, internal/api, and internal/monitoring all pass with 8 CPU burners saturating the host, the scenario that previously turned TestSLO_RollupTierBatchedFleet and four other budget tests red. |
||
|---|---|---|
| .. | ||
| alert_metrics.go | ||
| alert_metrics_test.go | ||
| norace_test.go | ||
| race_test.go | ||
| store.go | ||
| store_additional_test.go | ||
| store_bench_test.go | ||
| store_downsample_test.go | ||
| store_loadtest_test.go | ||
| store_query_plan_test.go | ||
| store_series_coverage_test.go | ||
| store_slo_test.go | ||
| store_test.go | ||