Repository navigation
docs(experiments): refresh E66 and B1 numbers after the E67 fix - #108
Merged
Merged
Conversation
E67 changed a bucket rule, so the two panels that could have moved were re-run on
the merged build instead of leaving stale numbers in the reports.
E66 (281-task generated panel), name bucket:
before E67 154/160 top-1, 157/160 any@8
after E67 157/160 top-1, 160/160 any@8
Exactly the three `src/core/test_impact.py` tasks the fix targets; the anchors
did not move (xerj 6/16, mcp_audit 11/17), so the calibration claim still holds.
B1 (commit localization, dev 71): identical - tool 19, neighbours 38, search 22,
grep 2 hit@5, paired +16. A classification fix should not move a benchmark that
does not touch it, and it did not.
Wilson cells for the E66 numbers are updated in `wilson.py`; every report now
quotes the build it was measured on.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
docs(experiments): refresh the E66 and B1 numbers after the E67 fix
E67 changed a bucket rule, so the two panels that could have moved were re-run on
the merged build instead of leaving stale numbers in the reports.
E66 (281-task generated panel), name bucket:
Exactly the three
src/core/test_impact.pytasks the fix targets; the anchorsdid not move (xerj 6/16, mcp_audit 11/17), so the calibration claim still holds.
B1 (commit localization, dev 71): identical - tool 19, neighbours 38, search 22,
grep 2 hit@5, paired +16. A classification fix should not move a benchmark that
does not touch it, and it did not.
Wilson cells for the E66 numbers are updated in
wilson.py; every report nowquotes the build it was measured on.