Rebase/inference usage on meta eval - #118
Merged
kargibora merged 13 commits intoSep 15, 2026
Merged
Conversation
ErlisLushtaku
approved these changes
Sep 9, 2026
This was referenced Sep 9, 2026
kargibora
force-pushed
the
rebase/inference-usage-on-meta-eval
branch
from
September 10, 2026 09:55
58d6791 to
d1ca639
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
JudgeArena discards token and cost information returned by model providers. Benchmark results therefore do not show the reported usage from generation and judging separately.
Changes
usagesection inrun-metadata.v1.json.How it works
The benchmark runner starts one tracking scope. Nested scopes share the same tracker, and the scope is reset when the run finishes or raises an error.
Generation calls use the
generationstage and judge calls usejudging. Meta-evaluation judges stored completions, so it normally reports only judging usage.Missing fields remain unknown. Coverage counts distinguish complete, partial, and unavailable usage. Malformed optional metadata does not prevent valid model responses from being returned.
Tracking scope
The tracker records successful responses returned by completed inference calls. These summaries describe observed usage, not a complete billing record. No benchmark scoring policy changes.
Tests
Tests cover canonical and fallback provider metadata, partial reporting, nested tracking, metadata output, failure cleanup, text/structured and sync/async compatibility, and local token counts.
Result:
395 passedlocally.Raw diff
Relative to #117 at
f30aac0. Parent changes are excluded. Pre-existing tests are restored; remaining test reductions apply only to stack-added coverage.