Skip to content

Add an output stream to goto-harness for parse_options_baset#3984

Merged
tautschnig merged 1 commit intodiffblue:developfrom
martin-cs:fix/redirect-exception-handler-output-4
Jan 28, 2019
Merged

Add an output stream to goto-harness for parse_options_baset#3984
tautschnig merged 1 commit intodiffblue:developfrom
martin-cs:fix/redirect-exception-handler-output-4

Conversation

@martin-cs
Copy link
Copy Markdown
Collaborator

Should fix the broken build on origin/develop. What happened was:

  1. Fix/redirect exception handler output 3 #3952 cleanly CIs.
  2. Add stub for new goto-harness tool [depends-on: #3920] #3875 gets merged which would break Fix/redirect exception handler output 3 #3952 but the CI is not re-run.
  3. Fix/redirect exception handler output 3 #3952 merged and thus the build is broken.
  • Each commit message has a non-empty body, explaining why the change was made.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • 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).
  • My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@tautschnig tautschnig merged commit b016d29 into diffblue:develop Jan 28, 2019
Copy link
Copy Markdown
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: 7c66df8).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/98886458
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.

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.

3 participants