)]}'
{"tox.ini":[{"author":{"_account_id":20297,"name":"duankebo","email":"duankebo@huawei.com","username":"duankebo"},"change_message_id":"fcb8a7d3e1420ae53b0c06081c681c424b59f664","unresolved":false,"context_lines":[{"line_number":20,"context_line":"basepython \u003d python2.7"},{"line_number":21,"context_line":"setenv \u003d OS_TEST_PATH\u003d./dragonflow/tests/fullstack"},{"line_number":22,"context_line":"commands \u003d"},{"line_number":23,"context_line":"  sh tools/pretty_tox_no_concurrency.sh \u0027{posargs}\u0027"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"[testenv:pep8]"},{"line_number":26,"context_line":"commands \u003d"}],"source_content_type":"text/x-properties","patch_set":1,"id":"9a061dce_8acbe0a4","line":23,"range":{"start_line":23,"start_character":21,"end_line":23,"end_character":26},"updated":"2016-04-06 08:06:32.000000000","message":"Will this means all the test cases will be executed in sequence? Can we create another test to run only these special test cases?","commit_id":"731fa21d9b45d6fec5dae23ee11cf89283a9bb6a"},{"author":{"_account_id":11343,"name":"Gal Sagie","email":"gal.sagie@gmail.com","username":"GalSagie"},"change_message_id":"877a305c342e060730b6cf3a90df3b7fc6e818c7","unresolved":false,"context_lines":[{"line_number":20,"context_line":"basepython \u003d python2.7"},{"line_number":21,"context_line":"setenv \u003d OS_TEST_PATH\u003d./dragonflow/tests/fullstack"},{"line_number":22,"context_line":"commands \u003d"},{"line_number":23,"context_line":"  sh tools/pretty_tox_no_concurrency.sh \u0027{posargs}\u0027"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"[testenv:pep8]"},{"line_number":26,"context_line":"commands \u003d"}],"source_content_type":"text/x-properties","patch_set":1,"id":"9a061dce_aa918454","line":23,"range":{"start_line":23,"start_character":21,"end_line":23,"end_character":26},"in_reply_to":"9a061dce_8acbe0a4","updated":"2016-04-06 08:10:45.000000000","message":"At first stage we run only fullstack tests in a sequence (not tempest which has 800-900 tests)\n\nThe intention in next stage is to add another job so we can split fullstacks to tests that cant run in concurrency and those who can.\n(But this require openstack-infra team approval so i dont want to block the reliable controller job on that, i will continue to send this patch for approval and then add the next stage)","commit_id":"731fa21d9b45d6fec5dae23ee11cf89283a9bb6a"}]}