You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking I should use my newfound free time productively, and figured I'd offer free effort to set you guys up with continuous proof-checking and the external CI. (This will help me understand how costly doing so "as a service" is.)
There are a couple of things to figure out before I embark on a long-dreaded dive into github actions' insanity. For my own proofs, I typically enjoy having the proof's main check with EasyCrypt's latest stable, and have all other branches check with EasyCrypt's main. (And we have a way of making exceptions for branches that should check with a specific EasyCrypt commit.)
Would that mode of checking work for youse?
The text was updated successfully, but these errors were encountered:
That sounds like a great idea! I tested this proof with the latest Easycrypt stable release and it worked. As I also don't expect there to be any wild and crazy branches, testing with main seems fine.
The proof does not go through with EasyCrypt main. Some problems with the cloning that are harder than my brain right now.
We will need at least one branch that checks with EasyCrypt main to set up the external CI. This could be this proof's main, of course, but then it needs fixed up.
Hi folks, (that's @mbbarbosa and @JoaoDiogoDuarte)
I'm thinking I should use my newfound free time productively, and figured I'd offer free effort to set you guys up with continuous proof-checking and the external CI. (This will help me understand how costly doing so "as a service" is.)
There are a couple of things to figure out before I embark on a long-dreaded dive into github actions' insanity. For my own proofs, I typically enjoy having the proof's
main
check with EasyCrypt's latest stable, and have all other branches check with EasyCrypt'smain
. (And we have a way of making exceptions for branches that should check with a specific EasyCrypt commit.)Would that mode of checking work for youse?
The text was updated successfully, but these errors were encountered: