-
Notifications
You must be signed in to change notification settings - Fork 33
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
Run benchmarks weekly in CI #1245
base: develop
Are you sure you want to change the base?
Conversation
|
||
.benchmarks_workflow: | ||
rules: | ||
- if: '$FULL_BUILD != "ON" && $BENCHMARKS_BUILD == "ON"' |
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.
We could alternatively use some sort of CI_WORKFLOW_TYPE
var which could be src, full, or benchmarks. That way we don't have to handle the two variables. I just don't have access to nightly build settings.
In a future PR I'll update the docs to explain how to properly view this data on SPOT, but it's more or less the following:
You'll notice at the moment each chart is practically a straight line, because there haven't been any changes to Serac yet. If you want to view another cluster or executable, click on the previous one to deselect it before selecting a new one. That way to you don't view both at the same time. |
…/serac into feature/chapman39/run-benchmarks-ci
…/serac into feature/chapman39/run-benchmarks-ci
This PR...
run_benchmarks.py
script that builds Serac, runs benchmarks, and moves resulting Caliper files in shared location on LC.Also,
specs.json
)physics_benchmark_solid_nonlinear_solve
benchmark to handle petsc being disabled