Fix SWE-Lancer token usage totals - #148
Open
sylvesterkaczmarek wants to merge 3 commits into
Open
Conversation
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
1 participant
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.
Summary
Remove the phantom one-token offset from SWE-Lancer aggregate usage metrics.
SWELancerEval.get_full_summary()currently initializes each aggregate token counter to1before adding the per-result grader usage. Every run therefore reports one extra input, output, and reasoning token, including an empty run.Fixes #139.
Fix
Initialize
total_input_tokens,total_output_tokens, andtotal_reasoning_tokensto zero before accumulation.Regression coverage
Adds a focused empty-summary regression verifying all three aggregate token totals are exactly zero when no results are present.
Per-result token extraction,
results.csvcontents, earned-value aggregation, and grading behavior are unchanged.