-
Notifications
You must be signed in to change notification settings - Fork 123
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
Initial implementation of check docstrings from python #1712
Conversation
Do you envision the timeout being for the entire check, or a timeout for each individual check in scope? If you're undecided, let me suggest the timeout should apply to each individual check. By this I mean that if a module has 10 checks, and we run |
Your idea makes sense. I'll take a look. I need to see how timeouts would interact with external solvers and their state but it seems like something we should be able to account for. |
Because different verification commands take different times for different configurations, automated testing and other use cases for
...or perhaps stored in a database of verification results and adapted based on completion time. |
This information is included in the REPL output as well as the remote API. By tracking empty cases we can help with generating coverage reports in a CI situation
dab7a1c
to
4b143d2
Compare
Check-point: docstrings can be checked from python
At a minimum work remains to update the documentation strings for this feature.