-
Notifications
You must be signed in to change notification settings - Fork 274
Run CBMC regression tests with --paths lifo in CI #3976
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
Conversation
+1 testing more options in CI / regressions A Good Thing. |
Restore namespace after symbolic execution [blocks: #3976]
Maintain nondet and dynamic counters across symex instances [blocks: #3976]
c6c187b
to
8e72f89
Compare
Single-path symex checker [blocks: #3976]
c6c187b
to
37bec93
Compare
37bec93
to
11db7b0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✔️
Passed Diffblue compatibility checks (cbmc commit: 11db7b0).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99712165
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✔️
Passed Diffblue compatibility checks (cbmc commit: 3310e02).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99716161
We were not regularly exercising this code outside unit tests, leading to regressions on several tests. On my system, running this additional test takes 42 seconds, which is still better than users running into issues. (ctest -V -L CORE -j8 takes an extra 10 seconds.) Fixes: diffblue#3956
On Codebuild we have seen "1.5222e-05s" when running in path-based mode.
3310e02
to
0bda456
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✔️
Passed Diffblue compatibility checks (cbmc commit: 0bda456).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99753724
We were not regularly exercising this code outside unit tests, leading to
regressions on several tests. On my system, running this additional test takes
42 seconds, which is still better than users running into issues. (ctest -V -L
CORE -j8 takes an extra 10 seconds.)
Fixes: #3956