)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"91285fb449e4a30e0eeef7e4b734498ccb77f2e8","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add 10 minutes to linuxbridge job"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Looking at a recent timeout at [1], the linuxbridge job was a few"},{"line_number":10,"context_line":"tests away from completing when the job timed out. The root cause"},{"line_number":11,"context_line":"of the timeout was actually devstack-gate-setup-workspace-new taking"},{"line_number":12,"context_line":"22 minutes instead of the 3-5 it should have which ate up a significant"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5f2577a7_16931e5d","line":9,"updated":"2017-09-15 20:20:55.000000000","message":"how about http://logs.openstack.org/64/502564/1/check/gate-tempest-dsvm-neutron-dvr-ubuntu-xenial/9fcef75/console.html#_2017-09-11_22_42_19_258347 ? It\u0027s not linuxbridge, but still timed out. Could it be that the problem is more general than just linuxbridge?","commit_id":"35048fc239736f4e0eabfa8875f57747c30a5b6f"}]}
