20260804 WorkHarness submission for gpt-5.4 - #21
Open
hylqll wants to merge 2 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.
Hi maintainers, thanks for reviewing the previous submission and for the detailed guidance.
This PR is a fresh submission update with a different model/result pair from the previous push, and it only includes the files needed for the benchmark handoff.
Summary
Add a clean aggregated submission for
gpt-5.4onworkharness, generated from run20260804_181758.This PR is a fresh submission update with a different model/result pair from the previous push, and it only includes the files needed for the benchmark handoff.
Included files
submissions/20260804_181758__gpt-5.4__workharness.jsondocs/workharness.mdsite/scripts/build_leaderboard.pyChanges
workharnessdescription explaining what the harness is and how it differs from existing harnesses.workharnessrenders correctly in the UI.