)]}'
{"driver_certs/cinder_driver_cert.sh":[{"author":{"_account_id":5196,"name":"Matthew Treinish","email":"mtreinish@kortar.org","username":"treinish"},"change_message_id":"f14da687c60b629949553cef8e66e386895bb4e1","unresolved":false,"context_lines":[{"line_number":75,"context_line":"# run tempest api/volume/test_*"},{"line_number":76,"context_line":"log_message \"Run the actual tempest volume tests (run_tempest.sh -N tempest.api.volume.test_*)...\", True"},{"line_number":77,"context_line":"exec 2\u003e \u003e(tee -a $TEMPFILE)"},{"line_number":78,"context_line":"`./run_tempest.sh -N tempest.api.volume.test_*`"},{"line_number":79,"context_line":"if [[ $? \u003d 0 ]]; then"},{"line_number":80,"context_line":"    log_message \"CONGRATULATIONS!!!  Device driver PASSED!\", True"},{"line_number":81,"context_line":"    log_message \"Submit output: ($TEMPFILE)\""}],"source_content_type":"text/x-sh","patch_set":1,"id":"AAAAUH%2F%2FQoM%3D","line":78,"updated":"2014-01-15 19:14:43.000000000","message":"Why are you using run_tempest.sh here? That script was really designed for running interactively, this is because it pipes the test output through colorizer.sh, which is pretty but has issues in things like jenkins console logs. Because of this I really don\u0027t recommend it for scripts unless the script is designed to be run only interactively. (I guess we can add a no-color option to run_tempest.sh to alleviate this)\n\nAlternatives to using run_tests would be using tox using either:\n\ntox -ealll api.volume\n\nor you can add a new volume tox job to tempest. Another option would be calling testr manually:\n\ntestr run --parallel api.volume\nor\n\npython setup.py testr --slowest --testr-args\u003d\"api.volume\"\n\nor if you want intermediate output (uncolorized that\u0027s Jenkins friendly, it\u0027s what we do in the gate through a tox job):\n\ntools/pretty_tox.sh api.volume\n\nAlso, I\u0027m curious would just using \"volume\" as the filter regex make more sense here (obviously it\u0027s outside the scope of this change). We have service tags in tempest so that if you filter on \"volume\" all the tests that call the cinder api outside the api.volumes dir (for example the scenario tests or nova api tests that use volumes) would get executed.","commit_id":"dd4f218f8158bfe10c16254cf636b779856459ec"}]}