Skip to content

Conversation

tautschnig
Copy link
Collaborator

GitHub reported "No event triggers defined in on" for github/workflows/benchcomp-config.yaml, which was never to define any GitHub actions in the first place. Move the Benchcomp config and the Benchcomp parser to a directory of their own to avoid these spurious warnings.

  • 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.

GitHub reported "No event triggers defined in `on`" for
`github/workflows/benchcomp-config.yaml`, which was never to define any
GitHub actions in the first place. Move the Benchcomp config and the
Benchcomp parser to a directory of their own to avoid these spurious
warnings.
Copy link

codecov bot commented Mar 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.64%. Comparing base (e7b0557) to head (b8f78a0).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #8250   +/-   ##
========================================
  Coverage    79.64%   79.64%           
========================================
  Files         1684     1684           
  Lines       195670   195670           
========================================
  Hits        155841   155841           
  Misses       39829    39829           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

With model-checking/kani#3090 we can use
variables and don't need to hack the PATH configuration into the command
line.
@tautschnig tautschnig merged commit e8ff03a into diffblue:develop Mar 23, 2024
@tautschnig tautschnig deleted the bugfixes/perf-event-triggers branch March 23, 2024 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants