We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Before, #450, testing/report.py was used to generate a failure exit code if the make test_all unit test target failed. See the call to report.py in the testing makefile (https://github.com/ibpsa/project1-boptest/blob/master/testing/makefile#L254) and the exit code spec set in report.py (https://github.com/ibpsa/project1-boptest/blob/master/testing/report.py#L84). With #450 implemented, this reporting now needs to be implemented in each job, otherwise, individual tests can fail but travis doesn't know about it, as has happened in this case: https://app.travis-ci.com/github/ibpsa/project1-boptest/jobs/578820097. This issue will fix this.
testing/report.py
make test_all
@kbenne this will need to be addressed in Service too.
The text was updated successfully, but these errors were encountered:
Merge pull request #467 from ibpsa/issue466_testingReporting
90aa88f
Closes #466
Closed by #467.
Sorry, something went wrong.
kbenne
dhblum
Successfully merging a pull request may close this issue.
Before, #450,
testing/report.py
was used to generate a failure exit code if themake test_all
unit test target failed. See the call to report.py in the testing makefile (https://github.com/ibpsa/project1-boptest/blob/master/testing/makefile#L254) and the exit code spec set in report.py (https://github.com/ibpsa/project1-boptest/blob/master/testing/report.py#L84). With #450 implemented, this reporting now needs to be implemented in each job, otherwise, individual tests can fail but travis doesn't know about it, as has happened in this case: https://app.travis-ci.com/github/ibpsa/project1-boptest/jobs/578820097. This issue will fix this.@kbenne this will need to be addressed in Service too.
The text was updated successfully, but these errors were encountered: