Skip to content

tests: parity reference for jevos-v3 - #25

Merged
feder-cr merged 1 commit into
mainfrom
golden-jevos-v3
Oct 2, 2026
Merged

feder-cr merged 1 commit into
mainfrom
golden-jevos-v3

Conversation

@feder-cr

@feder-cr feder-cr commented Oct 2, 2026

Copy link
Copy Markdown
Owner

The parity check compared jev with the Python server's answers on jevos-v2, so with jevos-v3 two cases moved by more than the 0.15 tolerance (0.265) and the release checks failed.

  • golden/jev-python-q8.json: P(yes) of the 200 answers from the Python server on jevos-v3-q8_0.gguf; the error bodies stay the original server's, with the served name updated (a newer FastAPI accepts a request without Content-Type, the original and jev refuse it).
  • check.py: jev is started with the name the reference answered with, not a fixed jevos-v2-q8_0.

Locally on Windows with jevos-v3: parity 212/212, largest P(yes) gap 0.058; every other check passes.

🤖 Generated with Claude Code

The reference answers were the Python server's on jevos-v2: with jevos-v3 two answers move by more than 0.15
(0.265), so CI failed. P(yes) of the 200 answers is now the Python server's on jevos-v3-q8_0; the error bodies
stay the original server's (a newer FastAPI answers a request without Content-Type), with the served name
updated. check.py starts jev with the name the reference answered with instead of a fixed jevos-v2-q8_0.
Locally: 212/212 cases, largest P(yes) gap 0.058; every other check passes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@feder-cr
feder-cr merged commit d48b9b7 into main Oct 2, 2026
6 checks passed
@feder-cr
feder-cr deleted the golden-jevos-v3 branch October 2, 2026 17:01
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.

1 participant