-
Notifications
You must be signed in to change notification settings - Fork 214
ContractModel: Report symbolic values as their symbolic names #452
ContractModel: Report symbolic values as their symbolic names #452
Conversation
5dd9e1d
to
45bff3e
Compare
@sjoerdvisscher in your own time. |
@sjoerdvisscher neither the local CI build failure or the hydra CI build failure makes any sense to me. Do you know what's goin on here? |
When it says "Killed" the build server probably ran out of memory. This seems to happen more frequently recently and it's really annoying since this result is cached. You could try to retrigger the build by making a small change in one of the mentioned modules. |
Is there no way to tell hydra to rebuild everything? |
Also, the golden tests in |
And local CI fails with nonsense logs like in the comment below. |
|
@michaelpj do you mind restarting hydra here? |
done |
dccd812
to
e33649a
Compare
@sjoerdvisscher do you mind merging this? |
Finally a real green PR again! (By the way, I did look at this yesterday, but since your last commit was "wip" I wasn't expecting it to be finished!) |
Oops, I think it was
|
* Report symbolic values as their symbolic names * fix build issue in tutorial * update golden test * wip * fix build issues * dependencies * update golden test * wip
This PR cleans up the counterexamples reported by
ContractModel
code to be a bit cleaner.Pre-submit checklist: