)]}'
{"jenkins/scripts/run-cover.sh":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"0d20bc9bfe51d4aa7f2c294285b35f32354165a8","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    fi"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"    ${PYTHON} - \u003c\u003cEOF \u003e ./testrepository.subunit"},{"line_number":26,"context_line":"import subunit.run"},{"line_number":27,"context_line":"from unittest import TestSuite"},{"line_number":28,"context_line":"from testtools import TestCase"},{"line_number":29,"context_line":"from testtools.content import content_from_file"}],"source_content_type":"text/x-sh","patch_set":2,"id":"fa31d9ce_84d94186","line":26,"updated":"2017-02-16 19:56:42.000000000","message":"Are you sure that os-testr is always installed or should we install it first?","commit_id":"cea618229d50c34a4da3ed103b9731fb64cf4031"},{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"b23e7c978c27c4f4f55c0fed9525590784896749","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    fi"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"    ${PYTHON} - \u003c\u003cEOF \u003e ./testrepository.subunit"},{"line_number":26,"context_line":"import subunit.run"},{"line_number":27,"context_line":"from unittest import TestSuite"},{"line_number":28,"context_line":"from testtools import TestCase"},{"line_number":29,"context_line":"from testtools.content import content_from_file"}],"source_content_type":"text/x-sh","patch_set":2,"id":"fa31d9ce_869dc65b","line":26,"in_reply_to":"fa31d9ce_84d94186","updated":"2017-02-16 20:36:38.000000000","message":"I think subunit \u0026 testtools will be brought in by testrepository so they should be there.  but, for this, we could use the os-testr environment which definitely has them.\n\n(p.s. os-testr does have a \"generate-subunit\" command-line tool that outputs a stream with a start/stop/runtime/status, but i could not find any practical way to enhance that to add this detail attachment; that part is all based on pulling mime parts out of a TestCase result from testtools and doesn\u0027t have simple \"add a file\" bindings)","commit_id":"cea618229d50c34a4da3ed103b9731fb64cf4031"},{"author":{"_account_id":5196,"name":"Matthew Treinish","email":"mtreinish@kortar.org","username":"treinish"},"change_message_id":"935cccd95c360b56396e5fc784e6d0fa9e5832e3","unresolved":false,"context_lines":[{"line_number":39,"context_line":"                       content_from_file(\u0027./cover/coverage.xml\u0027))"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"runner \u003d subunit.run.SubunitTestRunner()"},{"line_number":42,"context_line":"runner.run(TestSuite([TestCoverage(\u0027test_coverage\u0027)]))"},{"line_number":43,"context_line":"EOF"},{"line_number":44,"context_line":"}"},{"line_number":45,"context_line":""}],"source_content_type":"text/x-sh","patch_set":3,"id":"fa31d9ce_292a2de8","line":42,"updated":"2017-02-16 21:22:37.000000000","message":"So I\u0027d rather see this as a raw subunit attachment at appended to the end of the stream rather than being an attachment on a fake test. You can do this pretty easily with something like\n\n    file_name \u003d \u0027coverage.xml\u0027\n    stream \u003d subunit_v2.StreamResultToBytes(sys.stdout)\n    stream.startTestRun()\n    stream.status(file_name\u003dfile_name,\n                  file_bytes\u003dcontent_from_file(file_name),\n                  mime_type\u003d\u0027application/xml\u0027)\n    stream.stopTestRun()\n\nor something like that.","commit_id":"95294a6f6f89e880442a132165761070aa74f073"}]}