)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"4ab618ad5ec8468d986b9dfa88c8553342a2270c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b6792597_73556505","updated":"2026-07-20 11:19:32.000000000","message":"@mangust404@gmail.com Could we also merge this and https://review.opendev.org/c/openstack/trove-tempest-plugin/+/990132 to fix the missing test coverage ?\nThe required job renaming in master was already merged.","commit_id":"ab65b1a0837660df3e2dcaccddc01200d3d9e1ae"},{"author":{"_account_id":31737,"name":"Hirotaka Wakabayashi","email":"hiwkby@yahoo.com","username":"hiwkby"},"change_message_id":"614018d448d83986705c7eb21f2af831df8abfdd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d5b49498_f4dc23b3","updated":"2026-08-17 08:29:43.000000000","message":"Hello Takashi, Thanks for the PR.\n\nThis is a reasonable update to align our integration tests with the currently supported datastores (*1). It properly handles the removal of the dropped MySQL 5.7 job and adds the missing MariaDB and PostgreSQL jobs. All Zuul jobs are passing (SUCCESS).\n\nWhile splitting this commit was an option, keeping it as a single patch for \"updating supported DB tests\" is totally fine.\n\nPlease note that this patch should not be merged to the Epoxy branch, as MySQL 8.x is not supported there.\n\n(*1) https://docs.openstack.org/trove/latest/admin/datastore.html","commit_id":"ab65b1a0837660df3e2dcaccddc01200d3d9e1ae"},{"author":{"_account_id":31737,"name":"Hirotaka Wakabayashi","email":"hiwkby@yahoo.com","username":"hiwkby"},"change_message_id":"1a124ccc0a4154b0db529dc1002e9b278bb8ffcc","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f90c3b80_c55e6788","in_reply_to":"4a4dcaac_39fab1f6","updated":"2026-08-17 08:55:09.000000000","message":"Hello Eric and Takashi, I agree the 1-hour execution time needs improvement and might seem like \"overkill\" here.\n\nHowever, our current integration tests are quite flaky. This is a serious quality risk, as we might get used to random failures and miss real bugs.\n\nSince the trove repo is updated much more often, running tests in this plugin repo is highly valuable for quickly isolating whether a failure is a test-code bug or a real Trove bug. Therefore, I highly welcome it.","commit_id":"ab65b1a0837660df3e2dcaccddc01200d3d9e1ae"},{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"erkin.mussurmankulov@ps.kz","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"e455c40af25a2ce3f244cbc19c3a00807fe59de8","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f22f0b91_445caea1","in_reply_to":"b6792597_73556505","updated":"2026-07-20 11:34:02.000000000","message":"I don\u0027t see the point of running these tests here, since we already run them from the Trove repository itself.\n\nWe could implement some unit tests here instead, to cover tricky code. They would also be useful when upgrading to new Python versions. However, this may be too much work for relatively little benefit.\n\nRunning full integration scenarios here seems like overkill to me.\n\n@wchy1001@gmail.com @hiwkby@yahoo.com @ministry.96.nd@gmail.com\n\nWe should ask the full core developer team. What do you think, guys?\nDo we need to run integration tests in this repository?","commit_id":"ab65b1a0837660df3e2dcaccddc01200d3d9e1ae"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"d0cc5dcc5da0d04c70b01ccf85d6e5f30ae6e39f","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4a4dcaac_39fab1f6","in_reply_to":"f22f0b91_445caea1","updated":"2026-07-20 11:41:34.000000000","message":"\u003e since we already run them from the Trove repository itself.\n\nWithout these jobs in t-p-t repo, you already have to have a trove changes so that you run these jobs actually and verify any change being made in the tempest plugin side. For example if you accidentally merge a wrong test update then you may not catch it until you notice broken tempest tests when you check/propose a change to trove. That\u0027s definitely the point and benefit of having these jobs here.\n\nThis is the common pattern we see in the other tempest plugin.","commit_id":"ab65b1a0837660df3e2dcaccddc01200d3d9e1ae"}]}