-
Notifications
You must be signed in to change notification settings - Fork 1
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
automate benchmarking #2
Comments
Note that astropy does something clever (or confusing): the master branch are the actual benchmark tests (our mdanalysis/benchmarks), the results branch contains results (our benchmarks master), and any commits to their result branch trigger Travis, which automatically deploys the asv web site page to the gh-pages branch. |
It would be useful if the automated benchmarks did not re-run benchmarks that were already run. Ideally,
|
Possibly use
|
Or use (see https://asv.readthedocs.io/en/latest/using.html )
|
crontab is running daily 3:30am AZ = 10:30 GMT so results should become available a few minutes to a few hours later (depending on how many new commits/benchmarks were added). If something is not working properly, please open an issue. |
Performance benchmarking should be run continuously.
Current plan
Background
The text was updated successfully, but these errors were encountered: