Closed nrryuya closed 5 years ago
patrick.mackay [9:01 PM]
- update: we have addressed the issue with AWS and we are operational again. Thank you for your patience. Our apologies again for the disruption to your work. Have a great week.
At least, it seems to be necessary to skip llvm build ( https://github.com/kframework/evm-semantics/commit/465a97e15099ba1f7b6b27698fd23fd6d835b3ce ) and update k commit hash to 25e358c3a2cb9fa0156fbb81077eaeb88b24d689
or later (https://github.com/kframework/k/commit/25e358c3a2cb9fa0156fbb81077eaeb88b24d689 ) but after that, building process successes and proving some specs fails...
@yudetamago Thanks!
proving some specs fails
All specs fail? or some specs pass?
@nrryuya
All specs fail? or some specs pass?
The latter.
For example in ERC20 spec, allowance-spec.k
and totalSupply-spec.k
pass but
approve-spec.k
, transferFrom-success-2-spec.k
and transfer-success-2-spec.k
cause the following error.
(with 25e358c3a2cb9fa0156fbb81077eaeb88b24d689
k commit hash )
Initialization finished
==================================
Total time: 27.560
Parsing time: 25.779
Initialization time: 1.781
Execution time: 0.000
Init+Execution time: 1.781
query build time: 0.035 s
Z3 constraint time: 0.000 s
Z3 implication time: 0.603 s
Z3 implication queries: 30
resolveFunction time: 1.661 s
resolveFunction top-level calls: 8514
==================================
[Error] Internal: Uncaught exception thrown of type AssertionError.
Please rerun your program with the --debug flag to generate a stack trace, and
file a bug report at https://github.com/kframework/k/issues (null)
make: *** [specs/ERC20/transferFrom-success-2-spec.k.test] Error 1
The cause might be this issue. Could you retry with BYZANTIUM
?
https://github.com/kframework/evm-semantics/issues/287
ah, I'll try that 👍
BYZANTIUM
works 😉
Because of this K's issue, we remove
kprove
tests from CI for now.Copied from RV's public channel.
The current error.