You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(ci): use completed nightly runs for benchmark baseline, not just successful (#15806)
The benchmark baseline fetch was filtering workflow runs by status=success,
which only returns runs where EVERY job succeeded. When any single generator
E2E job fails, the entire nightly workflow is marked as failure, hiding valid
baseline data from all other generators.
This caused stale baselines — e.g., Swift E2E showed 307s (from old successful
runs) instead of ~700s (from recent runs that failed due to other generators).
Changes:
- Use status=completed + jq filter for success/failure conclusions, so runs
where some generators failed still contribute valid data for others
- Filter out entries with non-zero exit_code in lookup functions to avoid
including timings from failed generator runs
- Add tests for exit_code filtering
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: barry.zou <barry.zou@buildwithfern.com>
0 commit comments