Skip to content

Show only relevant benchmarks in CI summary#9

Draft
karkhaz wants to merge 1 commit intomainfrom
kk-no-show-empty
Draft

Show only relevant benchmarks in CI summary#9
karkhaz wants to merge 1 commit intomainfrom
kk-no-show-empty

Conversation

@karkhaz
Copy link
Owner

@karkhaz karkhaz commented Mar 27, 2024

This commit adds a new key to the benchcomp markdown table visualization. If delete_row_if_empty is set to true on a table's extra column, then for each benchmark, if the extra column evaluates to an empty string, then the benchmark will not be displayed in the table.

The change to the CI configuration means that benchmarks whose solver, symex, or total runtime changed by less than 10% will not be displayed in the tables for those metrics. The number of VCCs and number of program steps tables will also not contain benchmarks for which those numbers didn't change, and the success table will now only show benchmarks that are either newly passing or newly failing.

Please ensure your PR description includes the following:

  1. A description of how your changes improve Kani.
  2. Some context on the problem you are solving.
  3. A list of issues that are resolved by this PR.
  4. If you had to perform any manual test, please describe them.

Make sure you remove this list from the final PR description.

Resolves #ISSUE-NUMBER

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

This commit adds a new key to the benchcomp markdown table
visualization. If `delete_row_if_empty` is set to true on a table's
extra column, then for each benchmark, if the extra column evaluates to
an empty string, then the benchmark will not be displayed in the table.

The change to the CI configuration means that benchmarks whose
solver, symex, or total runtime changed by less than 10% will not be
displayed in the tables for those metrics. The number of VCCs and number
of program steps tables will also not contain benchmarks for which those
numbers didn't change, and the success table will now only show
benchmarks that are either newly passing or newly failing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant