Skip to content

New test checking that __CPROVER_havoc_object are detected as writes #6499

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

remi-delmas-3000
Copy link
Collaborator

New test checking that __CPROVER_havoc_object are detected as writes by assigns clause checking.

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

@codecov
Copy link

codecov bot commented Dec 3, 2021

Codecov Report

Merging #6499 (d8e5aac) into develop (7897cac) will decrease coverage by 0.19%.
The diff coverage is 66.21%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #6499      +/-   ##
===========================================
- Coverage    76.27%   76.07%   -0.20%     
===========================================
  Files         1546     1548       +2     
  Lines       165627   166362     +735     
===========================================
+ Hits        126329   126567     +238     
- Misses       39298    39795     +497     
Impacted Files Coverage Δ
jbmc/src/janalyzer/janalyzer_parse_options.cpp 48.25% <ø> (ø)
jbmc/src/jdiff/jdiff_parse_options.h 100.00% <ø> (ø)
src/goto-diff/goto_diff_parse_options.h 100.00% <ø> (ø)
...rc/goto-instrument/goto_instrument_parse_options.h 100.00% <ø> (ø)
src/analyses/goto_check_java.cpp 33.82% <33.82%> (ø)
src/analyses/goto_check.cpp 66.66% <66.66%> (-23.50%) ⬇️
src/analyses/goto_check_c.cpp 90.29% <90.29%> (ø)
jbmc/src/jbmc/jbmc_parse_options.cpp 72.32% <100.00%> (ø)
jbmc/src/jdiff/jdiff_parse_options.cpp 68.11% <100.00%> (ø)
src/ansi-c/c_typecheck_code.cpp 78.80% <100.00%> (ø)
... and 2 more

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 8ab933b...d8e5aac. Read the comment docs.

@tautschnig tautschnig merged commit adfd71d into diffblue:develop Dec 3, 2021
@feliperodri feliperodri added aws Bugs or features of importance to AWS CBMC users Code Contracts Function and loop contracts labels Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws Bugs or features of importance to AWS CBMC users Code Contracts Function and loop contracts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants