)]}'
{
  "log": [
    {
      "commit": "14f199eca26935cfe9306d9785a74d4a9e64ccb6",
      "tree": "616c33449baf8f6b0db4ebd5d878c715d211ecc8",
      "parents": [
        "422131d9520ec26e79a698cefdf98dc9a2c244ee"
      ],
      "author": {
        "name": "Ghanshyam Mann",
        "email": "gmann@ghanshyammann.com",
        "time": "Fri Dec 13 12:26:10 2024 -0800"
      },
      "committer": {
        "name": "Ghanshyam",
        "email": "gmann@ghanshyammann.com",
        "time": "Sat Dec 14 02:09:43 2024 +0000"
      },
      "message": "Run cindet-tempest-plugin tests in tempest-extra-tests\n\nWe have a lot of Tempest public interfaces which are used by the\ntempest plugins and sometime it is not easy to know breaking changes\nas we do not test all plugins test when any change merge in Tempest.\nExample: https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/937725\n\nTo avoid these breaking changes at some extend, let\u0027s run the cinder\ntempest plugin tests in one of the Temp[est job. Evantually, we can\nadd more plugins tests if needed but I think cinder-tempest-plugin\nuses a good amount of interfaces.\n\nChange-Id: I80c2b77936ac3220ff05232877eaf6fbac4743a5\n"
    },
    {
      "commit": "518e426ab4ff28db11654f8309241ab215b0e42b",
      "tree": "775683a9d8c9e28584ce436a0624383c5c18906f",
      "parents": [
        "e2183ca8f6562675ac0c31583be8316e4ffec161"
      ],
      "author": {
        "name": "Ghanshyam Mann",
        "email": "gmann@ghanshyammann.com",
        "time": "Fri Feb 10 19:57:36 2023 -0600"
      },
      "committer": {
        "name": "Ghanshyam",
        "email": "gmann@ghanshyammann.com",
        "time": "Sat Feb 11 19:05:34 2023 +0000"
      },
      "message": "Separate the extra tests to run in a separate job\n\nRecently we are seeing a lot of job timeout(bug#2004780)\nand we see many tests taking time and also number of tests\nincreasing over time. This is to prepare the list of extra tests\n(here extra tests means the tests which are covered by the other\nAPI or scenario tests) which we do not need to run in every\nintegrated jobs. Instead, we can run them in a separete job(s).\n\nCurrently I am adding admin (except keystone) and negative tests\nin the \u0027extra tests\u0027 list but we can add more tests here which\nwe think are covered in some other tests.\n\nAs negative tests are important for interop, adding those extra\ntests coverage for stable branch job also but running them in\nperiodic run only.\n\nRelated-Bug: #2004780\nChange-Id: Id02221df0d6180519751c63e890851bd59fdafa0\n"
    }
  ]
}