)]}'
{
  "commit": "b28b260d8335dd035e28f6a71cf3f6b016c01b3a",
  "tree": "17ca817efd6644231bcecb0bd08400d906107478",
  "parents": [
    "41a74431a234b59b3d3c78057b3fe2fe3c351e9d"
  ],
  "author": {
    "name": "Matt Riedemann",
    "email": "mriedem@us.ibm.com",
    "time": "Fri Jan 16 08:04:32 2015 -0800"
  },
  "committer": {
    "name": "Matt Riedemann",
    "email": "mriedem@us.ibm.com",
    "time": "Fri Jan 16 08:04:32 2015 -0800"
  },
  "message": "Add compute_quotas lock fixture to test_absolute_limits_negative\n\nThis has a negative test which tries to create a server with a number of\nmetadata items that exceed the quota limits but it intermittently\nfailing because the server gets created successfully (returns the 202).\n\nThis is most likely due to the quota class test which is making the\ndefault quotas unlimited when it runs so we can hit a window where this\nnegative test will fail.\n\nAnything compute tests in tempest which relies on quota checks for test\nresults should be using the compute_quotas lock fixture, so add that\nhere.\n\nCloses-Bug: #1411708\n\nChange-Id: Ic701b0dff2087002243d1ebc2ba8b4bd628d5eab\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b9176070430ce22251367f14931d200751624f55",
      "old_mode": 33188,
      "old_path": "tempest/api/compute/limits/test_absolute_limits_negative.py",
      "new_id": "d537d830db68b381b2bbd022e15c9a68bd41928b",
      "new_mode": 33188,
      "new_path": "tempest/api/compute/limits/test_absolute_limits_negative.py"
    }
  ]
}