-
Notifications
You must be signed in to change notification settings - Fork 162
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
Templates • Testing automation #3528
Conversation
- Clean validation models for VAV box.
…ssue3520_templateTesting
e6dbfdb
to
6ea5304
Compare
6ea5304
to
5984d6a
Compare
docker pull was not run before, hence simulations failing.
5f17768
to
fafb891
Compare
…ssue3520_templateTesting
…ssue3520_templateTesting
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.
@AntoineGautier : the setup for the testing looks good to me. I only added one inline comment as I am not sure what the best way is for configuring solver options. (The conf.yml
file is read by then the solver is hard coded.)
@mwetter This is ready to merge in my opinion. Crossing fingers that this will not destroy MBL CI testing. |
This closes #3520: please read the comments about time out and checksum verification on the issue page.
The high number of changed files is due to the fact that only one validation model is kept for each system type. All supported configurations are then generated with Python scripts by modifying this unique validation model.
The main developments from this PR are within
Buildings/Resources/Scripts/travis/templates
.This PR also includes some fixes needed to support some configurations that had not been validated before and that the new test workflow exposed as faulty. Most of these are related to #3526. The rest are due to missing parameters for the number of return and relief fans within the configuration record.
TODO before merging: