Skip to content

Pre-contracts whitespace changes #4326

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 2 commits into from
Mar 5, 2019

Conversation

karkhaz
Copy link
Collaborator

@karkhaz karkhaz commented Mar 4, 2019

I've decided to post this PR a few commits at a time, to make everybody's life easier, and so that I have a chance to actually audit the code.

This PR makes only whitespace changes. A lot of the actual code changes are quite subtle, so I'm going to get the whitespace changes out of the way first so that reviewers can focus on the code later.

klaas and others added 2 commits March 4, 2019 16:58
This commit is whitespace changes to code that will be changed in a
future commit. The code changes will all be fairly subtle, so this
commit aims to do the whitespace changes in advance to make reviewers'
lives easier.
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: 8afda0b).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/103125331
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.

@tautschnig tautschnig merged commit 5284894 into diffblue:develop Mar 5, 2019
@karkhaz karkhaz deleted the kk-non-functional branch March 5, 2019 13:09
@karkhaz
Copy link
Collaborator Author

karkhaz commented Mar 5, 2019

@allredj would you mind helping me understand why this PR and #4213 failed compatibility checks please? I don't think it's a force-push---perhaps because I've just become a 'collaborator' rather than a 'contributor'?

I'd like to be able to merge my PRs, but not sure if I should ignore these warnings. I'm not working at Diffblue, so I don't have access to travis.

@allredj
Copy link
Contributor

allredj commented Mar 5, 2019

@karkhaz The issue is that TG was already de-synchronised from CBMC when the check was done. There doesn't seem to be anything wrong with your PR in this regard.

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