-
Notifications
You must be signed in to change notification settings - Fork 132
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
Additional validation tests #210
Comments
Also configure a release testing branch where jenkins will run tests on all GPUs to ensure functionality. |
deferring |
BUILD_VALIDATION should be renamed so that it covers all long tests, not just validation ones. |
Bumping to the next feature release. |
While we can use the validation framework for some simulations, others require run times so long that we cannot run them in the CI framework - e.g. the hard disk equation of state in #985. We need to consider options for organizing these tests to run manually on HPC resources. One option would be a separate repository and use signac-flow to manage the jobs. |
As the plan is now to write a separate framework, this is not critical to complete before the 3.0.0 release. |
Some of the tests to include in validation:
|
Original report by me.
Pull request #278 along with a Jenkins reconfiguration paves the way for long running validation tests as part of hoomd's unit test suite. We need to expand the validation tests with additional tests for MD.
As part of this effort, I would like to simplify the cmake files. Currently we have a LOT of copied and pasted add_test code around. We could simplify that down to a simple macro which all the various cmake scripts call when they want to add a test.
The doumentation needs to be updated to describe the validation testing procedures, including a list of compile options and what hardware / compiler versions we officially validate.
The text was updated successfully, but these errors were encountered: