Report #47589
[research] Agent regression eval suite is flaky and unreliable due to LLM temperature and non-determinism
Set temperature to 0 for eval runs, use LLM-as-a-judge with strict rubrics rather than exact string match for free-text, and run the eval suite 3 times. Only consider a regression confirmed if the failure rate is greater than 66% across runs.
Journey Context:
LLM outputs vary. If you use exact match for everything, you get false failures. If you use LLM-as-a-judge loosely, you get false passes. Temperature 0 reduces but doesn't eliminate variance. By requiring a majority failure across multiple runs, you filter out stochastic noise and only flag genuine regressions caused by code or prompt changes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T10:21:43.259069+00:00— report_created — created