-
Notifications
You must be signed in to change notification settings - Fork 0
Tweak Ci proof-runner workflow #51
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
Conversation
* add some proofs with runtime < 1h as defaults * use self-hosted linux runners (normal) * always store artefacts after running * use timeout 2h for running the proof, ~3h for the daemon
…ng proofs, clean up artefacts
712f970 to
687c328
Compare
91a28a4 to
0a34390
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it! We can merge it first. I'm thinking that:
- Is it possible/okay to store the unfinished proof to continue proving? Could we store the proofs in KaaS? Any APIs?
- Should we provide automatic trigger to run all the proofs with different time out for different proofs?
We could maybe build something like that but it is better to just give a larger timeout. Otherwise we have to make sure things are compatible between the first and the following parts of the proof.
So far everything is manual. We can later schedule runs or have a controller gadget that starts the proof runs via |
Various changes to make the proof-running workflow work better:
This is a successful run of this workflow using two (short) proofs.
Here is another run (still in progress at the time of writing).