)]}'
{"bindep.txt":[{"author":{"_account_id":8770,"name":"Ken Giusti","email":"kgiusti@gmail.com","username":"kgiusti"},"change_message_id":"0667421d325674f505d7e7973df60cb088225e25","unresolved":false,"context_lines":[{"line_number":18,"context_line":"python-redis [platform:dpkg]"},{"line_number":19,"context_line":"zookeeperd [platform:dpkg]"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"# AMQP1 dpkg (qpidd/rabbit port conflict...)"},{"line_number":22,"context_line":"#qpidd [platform:dpkg]"},{"line_number":23,"context_line":"#sasl2-bin [platform:dpkg]"},{"line_number":24,"context_line":"#uuid-dev [platform:dpkg]"}],"source_content_type":"text/plain","patch_set":7,"id":"3a71b18c_b893caa2","line":21,"updated":"2016-12-01 20:28:09.000000000","message":"Interesting.  Are the brokers being started automatically?  I would not have expected that.  I thought only the setup-xx scripts would start their respective brokers.","commit_id":"4ccf7eb2c9813f90e09dc6bc90841a63d151d5e9"},{"author":{"_account_id":2813,"name":"Mehdi Abaakouk","email":"sileht@sileht.net","username":"sileht"},"change_message_id":"fb3c73b15986d9a6bf9d7fc132b6a7f0e1c65130","unresolved":false,"context_lines":[{"line_number":18,"context_line":"python-redis [platform:dpkg]"},{"line_number":19,"context_line":"zookeeperd [platform:dpkg]"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"# AMQP1 dpkg (qpidd/rabbit port conflict...)"},{"line_number":22,"context_line":"#qpidd [platform:dpkg]"},{"line_number":23,"context_line":"#sasl2-bin [platform:dpkg]"},{"line_number":24,"context_line":"#uuid-dev [platform:dpkg]"}],"source_content_type":"text/plain","patch_set":7,"id":"3a71b18c_b62587ac","line":21,"in_reply_to":"3a71b18c_b893caa2","updated":"2016-12-02 06:19:34.000000000","message":"Yeah, the system service start during package install...\n\nI need to figure out how we can solve this later.\nbindep allows to pass a profile and all pakcages here can be tagged with the profile. I think this is what we need, but infra script doesn\u0027t support to pass a profile to bindep, yet.\nI will ping some infra guys on this.","commit_id":"4ccf7eb2c9813f90e09dc6bc90841a63d151d5e9"}],"tools/test-setup.sh":[{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"e8a81903dfdca0316c0002c254e9d052e03b0fa3","unresolved":false,"context_lines":[{"line_number":16,"context_line":""},{"line_number":17,"context_line":"# Install more packages (need https://review.openstack.org/#/c/406037/)"},{"line_number":18,"context_line":"export BINDEP_PROFILE\u003d$(echo $JOB_NAME | cut -d- -f6)"},{"line_number":19,"context_line":"/usr/local/jenkins/slave_scripts/install-distro-packages.sh"}],"source_content_type":"text/x-sh","patch_set":14,"id":"3a71b18c_a405c046","line":19,"updated":"2016-12-06 14:52:51.000000000","message":"A major goal with abstracting test setup into a script like tools/test-setup.sh in your repo is that developers should expect to be able to run it to perform local setup tasks. Here instead you\u0027re embedding assumptions that this script only runs in our CI system (because you\u0027re calling other scripts from /usr/local/jenkins/slave_scripts which devs are unlikely to have locally and would mean needing to retrieve them from the project-config repo themselves to make this work).","commit_id":"db30926fb8e8dfd97002ab5a26da3f4ffcc1e03a"}]}