Repository navigation
fix(eval): exclude unreadable PortSwigger outcomes from solve rates - #117
Merged
elementalsouls merged 1 commit intoNov 16, 2026
Merged
elementalsouls merged 1 commit into
elementalsouls merged 1 commit into
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
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.
What does this change?
The automatic and parallel PortSwigger runners counted an expired or unreadable post-run lab as a failed solve. The manual runner already has an explicit ungraded state for the same condition. In a synthetic reproduction, a valid preflight and missing post-run widget produced a scored baseline failure.
Keep these records with solved=null and oracle_ok=false in both automated paths. Their cost remains visible, but the unreadable results fall outside the solve-rate denominator and cannot become parallel skills-retry candidates.
Validation