chore: cleanup duplicate GPT 5.2 Codex leaderboard entries#55
Open
Chesars wants to merge 1 commit intoSWE-bench:masterfrom
Open
chore: cleanup duplicate GPT 5.2 Codex leaderboard entries#55Chesars wants to merge 1 commit intoSWE-bench:masterfrom
Chesars wants to merge 1 commit intoSWE-bench:masterfrom
Conversation
…l leaderboards PR SWE-bench#50 manually added "GPT 5.2 Codex" entries to leaderboards.json, but the same model already existed as "GPT-5-2 Codex" (auto-generated from the experiments repo). This removes the manual duplicates (logs=null) and keeps the canonical entries from the pipeline.
Chesars
changed the title
Chesars
changed the title
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
leaderboards.json, but the same model already existed as "GPT-5-2 Codex" (auto-generated from experiments repo)logs: nullwhile the canonical entries have proper S3 log pathsDetails
GPT-5-2 Codex(72.8%, has logs)GPT 5.2 Codex(72.8%, logs=null)GPT-5-2 Codex(66.3%, has logs)GPT 5.2 Codex(66.3%, logs=null)