save benchmarks in results and use for aggregate coverage calculation #650
Conversation
This file contains 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
Saving the benchmark for each result has additional benefits than supporting the aggregate. It makes it easier to save results when auto-generation of benchmarks are used as part of the experiment (I use this a lot). Signed-off-by: David Korczynski <[email protected]>
|
/gcbrun exp -n d-cov-44 -b comparison -ns 4 -rd |
Signed-off-by: David Korczynski <[email protected]>
|
/gcbrun exp -n d-cov-45 -b comparison -ns 4 -rd |
Signed-off-by: David Korczynski <[email protected]>
|
Experiment is looking good, although there are some minor discrepancies still, but will look at those further down the line: https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-09-26-650-d-cov-45-comparison/index.html |
AdamKorcz
approved these changes
Sep 25, 2024
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.
This fixes the discrepancy mentioned here #645 (comment). Saving the benchmark for each result has additional benefits than supporting the aggregate. It makes it easier to save results when auto-generation of benchmarks are used as part of the experiment (I use this a lot).
Notice not the full benchmark
.yamlfrombenchmarks-set/...is set, but only the actual (one function or one test file) is saved per result dir.