-
Notifications
You must be signed in to change notification settings - Fork 831
Run kani daily on a schedule #1511
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
Running kani takes ages, instead of running it on every pull request we can just run it daily.
I don't actually know how to view the results of a the last scheduled run? |
I presume it should show up in the actions tab? It might require us to manually check the results |
In order for us to easily see the result of last nights kani run add a badge to the readme file.
Thanks @sanket1729, that gave me the idea of adding a badge to the readme. I've not done badges before so I just guessed based on: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge |
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.
ACK 3372333. Even if the badge is not displayed correctly, we can debug in follow up PRs.
It is possible to double-check it with a fork by replacing
https://github.com/$user/rust-bitcoin/actions/workflows/kani.yaml/badge.svg
, but looks correct to me.
It's possible to get github notifications for all CI runs, which I've turned on for this repo. Presumably I'll see these scheduled runs. The notifications are a little annoying since you get several of them every time a PR is merged ... but on the other hand they're easy to click away and it's nice to see the notification list rapidly shrink. There's probably a "only notify on failure" option. |
Th 8000 ere 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.
ACK 3372333
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.
ACK 3372333
Running kani takes ages, instead of running it on every pull request we can just run it daily.