Closed izgzhen closed 6 years ago
If you look at /tmp/countIssues.log
you should see the full call, but I think this should be enough to go on.
Also, unrelated: the extern
declaration should be "{x} == \"issue_tracking\""
. Variables need to be wrapped in braces to distinguish them from keywords in the target language (e.g. Java).
Also, unrelated: the extern declaration should be "{x} == \"issue_tracking\"". Variables need to be wrapped in braces to distinguish them from keywords in the target language (e.g. Java).
ah, I see. I think it is my typo.
This will take some time to address. Cozy assumes that Z3's model for uninterpreted functions is a mapping from inputs to outputs, with a default fallback value. (See mkfunc
in solver.py.) In reality, the default value in the mapping is a formula that can refer to inputs, meaning we have to do a lot more work to extract functions in the Z3 model as native Python objects.
I will continue working on this, but it is unlikely I will finish today.
Also, could you run python3 -c 'import z3; print(z3.get_version_string())'
and send me the output? On my machine this issue is caught earlier by an internal Z3 library routine. I think there might be a difference between our Z3 library versions.
Also, could you run python3 -c 'import z3; print(z3.get_version_string())' and send me the output? On my machine this issue is caught earlier by an internal Z3 library routine. I think there might be a difference between our Z3 library versions.
My version is 4.8.0
Thanks!
Hm, that's the same as me. Not sure what the difference is, then.
spec:
the
e
is printed by updatedraise ModelValidationError("model validation failed {}".format(e))
line, which I think is the samee
passed to thesatisfy
function.