)]}'
{
  "commit": "368d19d7e0240d7620950e2185a1cfa6f0437371",
  "tree": "474f2c2a92239fac714fe14314d5a9d1afd839ce",
  "parents": [
    "be79b46bb5b81cd433e780b12d96744434e82125"
  ],
  "author": {
    "name": "René Ribaud",
    "email": "rribaud@redhat.com",
    "time": "Wed May 10 14:35:09 2023 +0200"
  },
  "committer": {
    "name": "René Ribaud",
    "email": "rribaud@redhat.com",
    "time": "Wed May 10 14:49:38 2023 +0200"
  },
  "message": "Remove closure _unshelve_server not useful\n\nThe \"_unshelve_server\" method is not effective since it is executed\nafter tearDown, as it is scheduled with addCleanup. During the tearDown\nprocess, the \"server_check_teardown\" method waits for a server to be\nin the \"ACTIVE\" state. If a timeout occurs, the server is destroyed\nto create a new one and continue the test safely.\n\nTherefore, either the test exits tearDown with an \"ACTIVE\" server, in\nwhich case \"_unshelve_server\" will do nothing since it checks for a\n\"SHELVED\" server, or the server is destroyed upon exiting tearDown,\nand \"_unshelve_server\" raises an exception, as we can see in the\nstack trace for issue #2016957.\n\nRelated-Bug: #2016967\nChange-Id: Id34c82b001c77ba65ae987dc5eb6b925bc1b279f\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4049883ded1fe164fe0ec8cb05d5fc3c9baa3f2d",
      "old_mode": 33188,
      "old_path": "tempest/api/compute/servers/test_server_actions.py",
      "new_id": "e74ff189b6f7edc5a93a8dd5827798145f2025aa",
      "new_mode": 33188,
      "new_path": "tempest/api/compute/servers/test_server_actions.py"
    }
  ]
}