Skip to content

Silence warnings resulting from catch.hpp [blocks: #2310, #3425] #3876

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

Merged
merged 3 commits into from
Jan 22, 2019

Conversation

tautschnig
Copy link
Collaborator

This is factored out from #3425 in an attempt to get at least this bit approved and merged.

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

Wrap catch.hpp in a custom header use_catch.h that silences warnings, and make
all files use that header file instead.
This is to avoid direct inclusion of catch.hpp when use_catch.h should be used
instead. The first guard here is module_dependencies.txt, where only
testing-utils must have "catch" listed. The second line of defense is a macro
that must be set.
Do not impose formatting rules on imported code.
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫
This PR failed Diffblue compatibility checks (cbmc commit: 606ffdf).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/98117729
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

  • the cbmc commit has disappeared in the mean time (e.g. in a force-push)
  • the author is not in the list of contributors (e.g. first-time contributors).

The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.

@kroening
Copy link
Member

Would there be merit in upstreaming these changes to catch.hpp?

@thk123
Copy link
Contributor

thk123 commented Jan 22, 2019

This will need a manual TG bump - will create.

@tautschnig
Copy link
Collaborator Author

Would there be merit in upstreaming these changes to catch.hpp?

As in: fixing catch.hpp not to produce any warnings? Possibly so, but through the changes propose here we at least don't take any dependency on the proposals actually being picked up.

Half-related: I have a commit in the waiting to update catch.hpp to the most recent version, which will address the one local change we had made to catch.hpp earlier.

@tautschnig
Copy link
Collaborator Author

Thanks @thk123! Please just merge this PR when the corresponding TG change is ready.

@tautschnig tautschnig assigned thk123 and unassigned tautschnig Jan 22, 2019
@thk123 thk123 merged commit 9a6465b into diffblue:develop Jan 22, 2019
@thk123
Copy link
Contributor

thk123 commented Jan 22, 2019

@tautschnig done.

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.

4 participants