Skip to content

Run performance benchmarks as CI job #6690

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

tautschnig
Copy link
Collaborator

To guard against performance regressions introduced by changes, run a
fixed set (with this commit: the LLBMC benchmark suite) of benchmarks on
each pull request.

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@tautschnig tautschnig self-assigned this Feb 22, 2022
@codecov
Copy link

codecov bot commented Feb 22, 2022

Codecov Report

Merging #6690 (d067316) into develop (dea6182) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop    #6690   +/-   ##
========================================
  Coverage    76.90%   76.90%           
========================================
  Files         1590     1590           
  Lines       183963   183965    +2     
========================================
+ Hits        141477   141479    +2     
  Misses       42486    42486           
Impacted Files Coverage Δ
src/goto-symex/goto_symex_state.cpp 91.71% <100.00%> (+0.04%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e0afa1f...d067316. Read the comment docs.

@tautschnig tautschnig force-pushed the feature/ci-perf-benchmarking branch 12 times, most recently from ba9c562 to 1097d47 Compare February 22, 2022 15:58
@tautschnig tautschnig force-pushed the feature/ci-perf-benchmarking branch 2 times, most recently from 61f1256 to 7fa2775 Compare March 27, 2022 20:00
To guard against performance regressions introduced by changes, run a
fixed set (with this commit: the LLBMC benchmark suite) of benchmarks on
each pull request.
@tautschnig tautschnig force-pushed the feature/ci-perf-benchmarking branch from 7fa2775 to d067316 Compare March 28, 2022 20:54
@tautschnig tautschnig added the CI label Nov 8, 2022
@tautschnig
Copy link
Collaborator Author

Closing in favour of #8171.

@tautschnig tautschnig closed this Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant