Skip to content

Remove obsolete cbmc/fault_localization [blocks: 4216] #4215

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

Conversation

peterschrammel
Copy link
Member

@peterschrammel peterschrammel commented Feb 18, 2019

Replaced by goto-checker infrastructure

Based on #3970 - last 3 commits

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

@peterschrammel peterschrammel changed the title Remove obsolete cbmc/fault_localization [depends: 3970] Remove obsolete cbmc/fault_localization [depends: 3970, blocks: 4216] Feb 18, 2019
options, goto_model, ui_message_handler);
error() << "Given combination of command line arguments not supported"
<< eom;
exit(CPROVER_EXIT_USAGE_ERROR);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this even possible? The branching structure above makes it a bit hard to see, actually. Could else if please be used above to reduce indent? If it is genuinely possible, the error message should say which command line options are at fault for that.

Copy link
Member Author

@peterschrammel peterschrammel Mar 3, 2019

Choose a reason for hiding this comment

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

Alternative in 1b72e9a.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Can I ask for one level of indent by doing if(options.get_bool_option("localize-faults")) {...} else {...} to make the top level only decide on stop-on-fail+paths, in each of the (then) three cases?

Copy link
Member Author

Choose a reason for hiding this comment

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

See f157b2b

Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice! Which now makes clear that the final else is dead code, because you've enumerated all four combinations of paths/stop-on-fail.

@@ -5,7 +5,6 @@ SRC = all_properties.cpp \
cbmc_languages.cpp \
cbmc_main.cpp \
cbmc_parse_options.cpp \
fault_localization.cpp \
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can those Makefile changes please be in the same commit as the actual removal of the file?

@tautschnig tautschnig changed the title Remove obsolete cbmc/fault_localization [depends: 3970, blocks: 4216] Remove obsolete cbmc/fault_localization [blocks: 4216] Feb 21, 2019
@peterschrammel peterschrammel force-pushed the remove-bmct-fault-localization branch from fa25c94 to 126c0ab Compare March 3, 2019 21:31
@peterschrammel peterschrammel force-pushed the remove-bmct-fault-localization branch from 126c0ab to d9b910b Compare March 3, 2019 21:58
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: 126c0ab).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/102971681
Status will be re-evaluated on next push.
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 compatibility was already broken by an earlier merge.

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: d9b910b).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/102973053
Status will be re-evaluated on next push.
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 compatibility was already broken by an earlier merge.

@peterschrammel peterschrammel merged commit ce69f1d into diffblue:develop Mar 4, 2019
@peterschrammel peterschrammel deleted the remove-bmct-fault-localization branch March 4, 2019 07:27
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.

4 participants