)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"48e14a9767c0a758dd74acdfdc9d65a08142c4dd","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This reverts commit 82de75e83f1efdcb3d4c62648f33b374cfb27576."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The job still fails in gate [1], for different reasons. It also"},{"line_number":12,"context_line":"makes Icehouse broken again. Reverting the revert..."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"[1]: http://logs.openstack.org/53/157853/3/check/check-swift-dsvm-functional/489975b/console.html"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"ba7be1f8_303bdaec","line":11,"updated":"2015-02-27 18:40:03.000000000","message":"Have we figured out what the other reasons are?  When we disabled this before it was because we had some circular dependencies to unwedging the gate for icehouse, is that the case here or can some other change be made?","commit_id":"a5a5be22d729d7aacd8ca16a7e429acbed850e05"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"e0a3d7c3cd90ae91409ce72a188345d739f04bf0","unresolved":false,"context_lines":[{"line_number":12,"context_line":"makes Icehouse broken again. Reverting the revert..."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"[1]: http://logs.openstack.org/53/157853/3/check/check-swift-dsvm-functional/489975b/console.html"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Change-Id: I719029a1a202837ab778eed4f16b552bef6c4417"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"ba7be1f8_3012fa62","line":15,"updated":"2015-02-27 18:40:18.000000000","message":"Is there a bug for tracking the gate issue?","commit_id":"a5a5be22d729d7aacd8ca16a7e429acbed850e05"}],"zuul/layout.yaml":[{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"240bd363da08d2cf17632659d3046fe254607c56","unresolved":false,"context_lines":[{"line_number":890,"context_line":"  # TODO(cschwede): Enable voting when there is enough data"},{"line_number":891,"context_line":"  - name: check-swiftclient-dsvm-functional"},{"line_number":892,"context_line":"    voting: false"},{"line_number":893,"context_line":"  # TODO(ihrachys): temporarily disable to unblock gate"},{"line_number":894,"context_line":"  - name: check-swift-dsvm-functional"},{"line_number":895,"context_line":"    branch: ^(?!stable/icehouse).*$"},{"line_number":896,"context_line":"  - name: gate-swift-dsvm-functional"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"9a80dd14_5f3aef36","line":893,"updated":"2015-03-05 20:22:54.000000000","message":"So since this code block keeps getting deleted and pasted back in I would go with something clearer like:\n\n # when this code exists the jobs (run | don\u0027t run)\n\nit is hard to follow the breadcrumb trail. The use of reintroduce in a commit message of a patch intended to remove a job (I think?) doesn\u0027t help matters.","commit_id":"84a5fddfc701ab687a6ebaddbc891cbdb3bf217b"}]}