Skip to content

fix: reject negative or NaN compareRuns tolerance - #42

Merged
royalpinto007 merged 1 commit into
AgentPostmortem:mainfrom
sharadvc:cursor/fix-compare-tolerance-8734
Sep 12, 2026
Merged

royalpinto007 merged 1 commit into
AgentPostmortem:mainfrom
sharadvc:cursor/fix-compare-tolerance-8734

Conversation

@sharadvc

Copy link
Copy Markdown
Contributor

Summary

compareRuns now rejects non-finite or negative tolerance values with CompareValidationError instead of accepting them.

Test plan

  • npm test — includes negative and NaN tolerance cases

Fixes #30

Validate tolerance is a non-negative finite number before comparing runs.
Negative tolerance could mark improvements as regressions; NaN disabled
regression detection entirely.

Co-authored-by: Sharad. <sharadvc@users.noreply.github.com>
@royalpinto007
royalpinto007 merged commit c0fd797 into AgentPostmortem:main Sep 12, 2026
9 checks passed
@github-actions

Copy link
Copy Markdown

Nice work @sharadvc, this is merged.

Good, focused change. Exactly the kind of thing Evalgate needs.

If Evalgate is useful to you, a star goes a long way.

Happy to see more from you whenever you have the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

compareRuns accepts negative/NaN tolerance

2 participants