Difference between revisions of "NeutronThirdPartyTesting"
(→Log & Test Results filesystem layout) |
(→Log & Test Results Filesystem Layout) |
||
Line 3: | Line 3: | ||
== Log & Test Results Filesystem Layout == | == Log & Test Results Filesystem Layout == | ||
− | Third-Party CI systems '''MUST''' provide logs and configuration data to help developers troubleshoot test failures. A third-party CI that '''DOES NOT''' post logs should be a candidate for removal | + | Third-Party CI systems '''MUST''' provide logs and configuration data to help developers troubleshoot test failures. A third-party CI that '''DOES NOT''' post logs should be a candidate for removal, and new CI systems '''MUST''' post logs before they can be awarded voting privileges. |
Third party CI systems should follow the filesystem layout convention of the OpenStack CI system | Third party CI systems should follow the filesystem layout convention of the OpenStack CI system |
Revision as of 21:10, 9 June 2014
This page documents the requirements, expectations, and ideally the results of all third party testing done by open source and vendor plugins for the Neutron project.
Log & Test Results Filesystem Layout
Third-Party CI systems MUST provide logs and configuration data to help developers troubleshoot test failures. A third-party CI that DOES NOT post logs should be a candidate for removal, and new CI systems MUST post logs before they can be awarded voting privileges.
Third party CI systems should follow the filesystem layout convention of the OpenStack CI system
At the root of the results - there should be the following:
- console.html.gz - contains the output of stdout of the test run
- logs/
Logs must be a directory, which contains the following:
- Log files for each screen session that DevStack creates and launches an OpenStack component in
- Test result files
- testr_results.html.gz
- tempest.txt.gz