Skip to content
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

Merged
merged 49 commits into from
Feb 7, 2024
Merged

Templates • Testing automation #3528

merged 49 commits into from
Feb 7, 2024

Conversation

AntoineGautier
Copy link
Contributor

@AntoineGautier AntoineGautier commented Sep 19, 2023

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:

@AntoineGautier AntoineGautier force-pushed the issue3520_templateTesting branch 2 times, most recently from e6dbfdb to 6ea5304 Compare September 20, 2023 08:56
@AntoineGautier AntoineGautier force-pushed the issue3520_templateTesting branch from 6ea5304 to 5984d6a Compare September 20, 2023 15:36
@AntoineGautier AntoineGautier changed the title Issue3520 template testing Templates • Testing automation Sep 27, 2023
Copy link
Member

@mwetter mwetter left a 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.)

@AntoineGautier
Copy link
Contributor Author

@mwetter This is ready to merge in my opinion. Crossing fingers that this will not destroy MBL CI testing.

@mwetter mwetter merged commit a4a1b56 into master Feb 7, 2024
2 checks passed
@mwetter mwetter deleted the issue3520_templateTesting branch February 7, 2024 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Templates • Automate VAV template testing
2 participants