-
Notifications
You must be signed in to change notification settings - Fork 0
Nightly or weekly end-to-end tester and benchmarker #164
Comments
start out with just the 2 core machines, and then upgrade to a larger machine if it seems like a useful thing to do. |
what i'd like to run:
how: run them through the ipython interface so that we can "%run notebook.ipynb"
then we can access variables from the notebook and check their values. then we can also inject some benchmarking code use line_profiler? or something else? and see how long each step takes to run. look into external examples of uploading this data somewhere so that we can look at benchmark evolution over time. |
will run tests through ipython so that we have access to the IPython shell. another issue:
|
|
Running this on GitHub-hosted actions runners on a daily or weekly basis would be wonderful. It seems like GPU-enabled actions runners are in beta? github/roadmap#505 |
This might be more of a 2023 task but I was learning about stuff and figured it would be good to write down my notes. inspiration: https://pv.github.io/numpy-bench/ learn about ASV: https://asv.readthedocs.io/en/stable/using.html |
https://stackoverflow.com/questions/63014786/how-to-schedule-a-github-actions-nightly-build-but-run-it-only-when-there-where
see also:
#15
#75
The text was updated successfully, but these errors were encountered: