Skip to content

Conversation

@jberthold
Copy link
Member

@jberthold jberthold commented Oct 15, 2025

Various changes to make the proof-running workflow work better:

  • using self-hosted (normal linux) runners
  • configurable timeout (default 2h)
  • no default p-token image hash, selected from the submodule instead

This is a successful run of this workflow using two (short) proofs.
Here is another run (still in progress at the time of writing).

@jberthold jberthold force-pushed the CI-proof-runner-tweaks branch from 712f970 to 687c328 Compare October 15, 2025 04:07
@jberthold jberthold force-pushed the CI-proof-runner-tweaks branch from 91a28a4 to 0a34390 Compare October 15, 2025 04:18
@jberthold jberthold marked this pull request as ready for review October 15, 2025 04:27
Copy link

@Stevengre Stevengre left a 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:

  1. Is it possible/okay to store the unfinished proof to continue proving? Could we store the proofs in KaaS? Any APIs?
  2. Should we provide automatic trigger to run all the proofs with different time out for different proofs?

@jberthold
Copy link
Member Author

  1. Is it possible/okay to store the unfinished proof to continue proving? Could we store the proofs in KaaS? Any APIs?

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.

  1. Should we provide automatic trigger to run all the proofs with different time out for different proofs?

So far everything is manual. We can later schedule runs or have a controller gadget that starts the proof runs via gh application.

@jberthold jberthold merged commit b66d694 into proofs Oct 15, 2025
4 checks passed
@jberthold jberthold deleted the CI-proof-runner-tweaks branch October 17, 2025 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants