)]}'
{".testr.conf":[{"author":{"_account_id":11816,"name":"mike bayer","display_name":"Mike Bayer","email":"mike_mp@zzzcomputing.com","username":"zzzeek","status":"Red Hat"},"change_message_id":"60869536e227f6d472a09fd52609844c51baa80f","unresolved":false,"context_lines":[{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"},{"line_number":13,"context_line":"# for details."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"instance_provision\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision create $INSTANCE_COUNT"},{"line_number":16,"context_line":"instance_dispose\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision drop $INSTANCE_IDS"}],"source_content_type":"text/plain","patch_set":2,"id":"baada198_ea798931","line":13,"updated":"2014-07-15 23:22:48.000000000","message":"so what we\u0027re going to need is to be able to spin up 10 mysql databases, *and* 10 postgresql databases, *and* etc. etc., and also handle cleanup/teardown within a schema since I\u0027d prefer some flexibility with how that is done on a per-suite basis.  if we make provision.py smarter, the testr feature here may not be needed...all provision.py needs to do is hand out engines.  though testr\u0027s feature here is providing per-test-run setup/teardown and if we cant get that any other way, we still might need to keep this.","commit_id":"0561dddb8af3a807d1278c406596031fdb3d312d"},{"author":{"_account_id":11816,"name":"mike bayer","display_name":"Mike Bayer","email":"mike_mp@zzzcomputing.com","username":"zzzeek","status":"Red Hat"},"change_message_id":"64065947a2df1f472291be9bc607413eec09054c","unresolved":false,"context_lines":[{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"},{"line_number":13,"context_line":"# for details."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"instance_provision\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision create $INSTANCE_COUNT"},{"line_number":16,"context_line":"instance_dispose\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision drop $INSTANCE_IDS"}],"source_content_type":"text/plain","patch_set":2,"id":"baada198_f7074cc7","line":13,"in_reply_to":"baada198_07386bd3","updated":"2014-07-17 22:13:44.000000000","message":"Roman - here\u0027s the thing.  if provision can create databases that last throughout many test suites, e.g. many test classes/modules, whats the mechanism by which those databases are dropped when the test run ends?   testr doesn\u0027t seem to have any other options in this regard.  we could perhaps use module-level hooks, which means schemas last throughout the scope of a whole module, that might be good enough.\n\nbasically I want to get away from \"drop the schema in tearDown\" and I also dont want to \"drop the schema in tearDownClass\".  provisioner should be able to keep track of a handful of schemas for the whole test run.","commit_id":"0561dddb8af3a807d1278c406596031fdb3d312d"},{"author":{"_account_id":11816,"name":"mike bayer","display_name":"Mike Bayer","email":"mike_mp@zzzcomputing.com","username":"zzzeek","status":"Red Hat"},"change_message_id":"2b1dc671732b80d166124f5babbbd94a93334825","unresolved":false,"context_lines":[{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"},{"line_number":13,"context_line":"# for details."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"instance_provision\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision create $INSTANCE_COUNT"},{"line_number":16,"context_line":"instance_dispose\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision drop $INSTANCE_IDS"}],"source_content_type":"text/plain","patch_set":2,"id":"baada198_c9a1afaa","line":13,"in_reply_to":"baada198_a9301408","updated":"2014-07-18 17:23:10.000000000","message":"i\u0027ve commented on the bug https://bugs.launchpad.net/oslo/+bug/1339206 with an outline of what I\u0027m thinking at the moment.\n\nshort answer is yes provision create/drop will hand out/tear down N number of schemas x M number of database backends.\n\nadding mysql/pg/etc. to tox requirements, not sure about that.  the idea is that the external environment can add backends as needed.  if an env has cx_Oracle installed, it can add an Oracle URL to the environment and it will be tested on those tests that don\u0027t exclude it.\n\n\u003e running mysqld and postgresql server binaries simultaneously, \n\nOver here: http://jenkins.sqlalchemy.org/ I run Postgresql, Mysql, Oracle Express all on the same amazon EC2 small instance (which is way too small in general, but works fine) simultaneously.  When they are idle, they don\u0027t use up many resources (pg and Mysql use almost none).\n\nBut that doesn\u0027t matter here.  By allowing the test environment to specify *where* these databases are with full URLs, every DB can be somewhere else.  There\u0027s no \"probing\" going on.","commit_id":"0561dddb8af3a807d1278c406596031fdb3d312d"},{"author":{"_account_id":6849,"name":"Roman Podoliaka","email":"roman.podoliaka@gmail.com","username":"rpodolyaka"},"change_message_id":"97668cea79ec3603ec4c78a7e8df60e0d2b2421a","unresolved":false,"context_lines":[{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"},{"line_number":13,"context_line":"# for details."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"instance_provision\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision create $INSTANCE_COUNT"},{"line_number":16,"context_line":"instance_dispose\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision drop $INSTANCE_IDS"}],"source_content_type":"text/plain","patch_set":2,"id":"baada198_07386bd3","line":13,"in_reply_to":"baada198_ea798931","updated":"2014-07-16 07:31:40.000000000","message":"Being an author of the original patch to oslo-incubator I agree with Mike here on that it would be great to make provision.py smarter and handle all this stuff there, so that we wouldn\u0027t need to change .testr.conf in each project.\n\nAngus, could you please volunteer to try that approach first before we merge this?","commit_id":"0561dddb8af3a807d1278c406596031fdb3d312d"},{"author":{"_account_id":11279,"name":"Angus Lees","email":"gus@inodes.org","username":"gus"},"change_message_id":"f7384cb539319d5a95a2bc998fb79144742473de","unresolved":false,"context_lines":[{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"},{"line_number":13,"context_line":"# for details."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"instance_provision\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision create $INSTANCE_COUNT"},{"line_number":16,"context_line":"instance_dispose\u003d${PYTHON:-python} -m oslo.db.sqlalchemy.provision drop $INSTANCE_IDS"}],"source_content_type":"text/plain","patch_set":2,"id":"baada198_a9301408","line":13,"in_reply_to":"baada198_f7074cc7","updated":"2014-07-18 06:21:35.000000000","message":"I\u0027m lost - what do we want testr to do, and what do we want provision.py to do?\n\n.. and what lifetimes do we want?  I\u0027m also confused what isolation / parallelism is desired in the above :/\n\nI can make provision.py create, hand out, and later destroy 1- mysql, 10 pg, etc databases easily enough.  If I understand this correctly, this means adding mysql-server, postgresql-server, etc to the tox test requirements - is that even possible?\n\n.. or perhaps provision.py should probe for binaries, and only return them if they\u0027re already installed?  That would be easy enough.  During \"provision.py create\" I should be able to start instances of each of these servers in a temporary directory, create databases, and hand out URLs.  Then during \"provision.py drop\", kill the servers and delete the temp datastore directories.\n\nIs that what we\u0027re talking about here?\n\nI _think_ this means running mysqld and postgresql server binaries simultaneously, which requires more ram on your dev machines (though it should be ok).  This won\u0027t scale to \"and oracle, and sybase, and ...\" however.","commit_id":"0561dddb8af3a807d1278c406596031fdb3d312d"},{"author":{"_account_id":7536,"name":"Ilya Pekelny","email":"ipekelny@mirantis.com","username":"I159"},"change_message_id":"e1acd763656e2c7a8aa5ca58cae6ae2a645554c1","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"test_id_option\u003d--load-list $IDFILE"},{"line_number":8,"context_line":"test_list_option\u003d--list"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"}],"source_content_type":"text/plain","patch_set":4,"id":"baada198_33450a6f","line":9,"updated":"2014-07-21 10:20:40.000000000","message":"My opinion — we don\u0027t need it. We use opportunistic approach for a long time. If you want to override OS_TEST_DBAPI_ADMIN_CONNECTION, you can do it in your environment. Other databases are temporary and tests use it opportunistically, please seehttps://github.com/openstack/oslo.db/blob/master/oslo/db/sqlalchemy/test_base.py#L97.  Lately I use everywhere in review.openstack, irc e.t.c. my old weird nick — \"I159\".","commit_id":"5ab4b5ba6d060388a021dfad5548a07728361efa"},{"author":{"_account_id":11279,"name":"Angus Lees","email":"gus@inodes.org","username":"gus"},"change_message_id":"021825b0f40f7854b0448de34a1a7ae4cc31dfe7","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"test_id_option\u003d--load-list $IDFILE"},{"line_number":8,"context_line":"test_list_option\u003d--list"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"}],"source_content_type":"text/plain","patch_set":4,"id":"baada198_d6e73510","line":9,"in_reply_to":"baada198_33450a6f","updated":"2014-07-22 01:06:03.000000000","message":"Yeah, I could be convinced by this.\n\nThe Opportunistic classes still only test particular drivers (and other options).  I can certainly manually edit that class every time I want to test some other arrangement - and I can extend the list of Opportunistic classes if I want to make that test combination permanent easily enough.","commit_id":"5ab4b5ba6d060388a021dfad5548a07728361efa"},{"author":{"_account_id":7536,"name":"Ilya Pekelny","email":"ipekelny@mirantis.com","username":"I159"},"change_message_id":"fb495acb4a61900a52d085df6c2c12d52c41bfb9","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"test_id_option\u003d--load-list $IDFILE"},{"line_number":8,"context_line":"test_list_option\u003d--list"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"}],"source_content_type":"text/plain","patch_set":4,"id":"baada198_7eb8e975","line":9,"in_reply_to":"baada198_8aa3be9c","updated":"2014-07-22 09:01:05.000000000","message":"Well, I found corresponding mail list, and now I think I\u0027ve got your idea. Please, change my nick to I159 or put your nick here ;)","commit_id":"5ab4b5ba6d060388a021dfad5548a07728361efa"},{"author":{"_account_id":7536,"name":"Ilya Pekelny","email":"ipekelny@mirantis.com","username":"I159"},"change_message_id":"76305555a0e67bcc31386f26299a3dc5e7b93166","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"test_id_option\u003d--load-list $IDFILE"},{"line_number":8,"context_line":"test_list_option\u003d--list"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"# NOTE(ipekelny): create an isolated DB instance for each test running process"},{"line_number":11,"context_line":"# to prevent race conditions. Please see"},{"line_number":12,"context_line":"# https://testrepository.readthedocs.org/en/latest/MANUAL.html#remote-or-isolated-test-environments"}],"source_content_type":"text/plain","patch_set":4,"id":"baada198_8aa3be9c","line":9,"in_reply_to":"baada198_d6e73510","updated":"2014-07-22 08:22:22.000000000","message":"Yep, you can extend it, if you think that the Opp. test cases too rigid, you can propose some changes to it. But I don\u0027t know why do you merge this old code here? Can you describe it, please?\nNow we create temporary databases for every test run.","commit_id":"5ab4b5ba6d060388a021dfad5548a07728361efa"}],"README.rst":[{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c20f61dca9e37cd97521be5e6031dac2969b5d15","unresolved":false,"context_lines":[{"line_number":9,"context_line":"* Source: http://git.openstack.org/cgit/openstack/oslo.db"},{"line_number":10,"context_line":"* Bugs: http://bugs.launchpad.net/oslo"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Running Tests"},{"line_number":13,"context_line":"-------------"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"To run tests in virtualenvs (preferred)::"}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_0c11b25c","line":12,"updated":"2014-07-14 20:27:21.000000000","message":"This should probably go into the doc/source tree somewhere instead of in the readme. Maybe in contributing.rst below the import?","commit_id":"f2f9d31bb3ebcda6907b62e2d4b1a99d6f004d5f"},{"author":{"_account_id":11279,"name":"Angus Lees","email":"gus@inodes.org","username":"gus"},"change_message_id":"4d4c083ea118aa65d1d02cd3d208525c173d79a0","unresolved":false,"context_lines":[{"line_number":9,"context_line":"* Source: http://git.openstack.org/cgit/openstack/oslo.db"},{"line_number":10,"context_line":"* Bugs: http://bugs.launchpad.net/oslo"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Running Tests"},{"line_number":13,"context_line":"-------------"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"To run tests in virtualenvs (preferred)::"}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_b21e545d","line":12,"in_reply_to":"baada198_0c11b25c","updated":"2014-07-15 01:20:06.000000000","message":"Moved to CONTRIBUTING.rst","commit_id":"f2f9d31bb3ebcda6907b62e2d4b1a99d6f004d5f"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c20f61dca9e37cd97521be5e6031dac2969b5d15","unresolved":false,"context_lines":[{"line_number":20,"context_line":"To run tests in the current environment::"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"  sudo pip install -r requirements.txt"},{"line_number":23,"context_line":"  nosetests"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"To run tests using MySQL or PostgreSQL as a DB backend do::"},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_6c5b0e54","line":23,"updated":"2014-07-14 20:27:21.000000000","message":"It might work for now, but we don\u0027t want people doing this because nose and testr have different test discovery behavior and that tends to cause the tests to break under nose.\n\nYou could replace this line with\n\n  python setup.py testr\n\ninstead.","commit_id":"f2f9d31bb3ebcda6907b62e2d4b1a99d6f004d5f"},{"author":{"_account_id":11279,"name":"Angus Lees","email":"gus@inodes.org","username":"gus"},"change_message_id":"4d4c083ea118aa65d1d02cd3d208525c173d79a0","unresolved":false,"context_lines":[{"line_number":20,"context_line":"To run tests in the current environment::"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"  sudo pip install -r requirements.txt"},{"line_number":23,"context_line":"  nosetests"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"To run tests using MySQL or PostgreSQL as a DB backend do::"},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_d221089f","line":23,"in_reply_to":"baada198_6c5b0e54","updated":"2014-07-15 01:20:06.000000000","message":"Done","commit_id":"f2f9d31bb3ebcda6907b62e2d4b1a99d6f004d5f"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c20f61dca9e37cd97521be5e6031dac2969b5d15","unresolved":false,"context_lines":[{"line_number":26,"context_line":""},{"line_number":27,"context_line":"  OS_TEST_DBAPI_ADMIN_CONNECTION\u003dmysql://user:password@host/database tox -e py27"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Note, that your DB user must have permissions to create and drop databases."}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_acffe600","line":29,"updated":"2014-07-14 20:27:21.000000000","message":"Use the \"note\" directive here.\n\n  .. note:: Your DB user must have permissions to create and drop databases.","commit_id":"f2f9d31bb3ebcda6907b62e2d4b1a99d6f004d5f"},{"author":{"_account_id":11279,"name":"Angus Lees","email":"gus@inodes.org","username":"gus"},"change_message_id":"4d4c083ea118aa65d1d02cd3d208525c173d79a0","unresolved":false,"context_lines":[{"line_number":26,"context_line":""},{"line_number":27,"context_line":"  OS_TEST_DBAPI_ADMIN_CONNECTION\u003dmysql://user:password@host/database tox -e py27"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Note, that your DB user must have permissions to create and drop databases."}],"source_content_type":"text/x-rst","patch_set":1,"id":"baada198_52b25849","line":29,"in_reply_to":"baada198_acffe600","updated":"2014-07-15 01:20:06.000000000","message":"Done","commit_id":"f2f9d31bb3ebcda6907b62e2d4b1a99d6f004d5f"}]}
