-
Notifications
You must be signed in to change notification settings - Fork 6
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
Unable to prove SPDM spec #767
Comments
I can reproduce this. SPARK just slowly eats all memory. The |
I ran the prove again with the commit 0c040681337d4c8a7a9a4dd0231289cc72391c5c from SPDM and dd4eb1b from RecordFlux. This is the result: The general memory usage seems to have improved, with -j48 it's most of the time using ~130GB (instead of >250GB before). However there is a single gnatwhy3 process running eating the whole 1TB until the proof stops. |
Great, thanks! I can see that the proofs of the various |
spdm.tar.gz |
I can still see the old code generation there ... can you please make sure you have RecordFlux commit 9bd0260 and try again? |
I forgot to pull the latest commit. spdm.tar.gz is hopefully up to date now. |
Thanks. Forgot to say that I am now able to generate the code myself from the SPDM repo directly. |
Not a RecordFlux ticket. |
I tried to prove our current spec for SPDM. The proof was done with the generated code, spec and project file in spdm.tar.gz. The results are included in spdm.log.
The text was updated successfully, but these errors were encountered: