)]}'
{
  "commit": "0ae551fdf57ecdd95963e683c9eccbb5dfdf43c4",
  "tree": "69e616838ae93ecb204e9b51080548c5e2229d39",
  "parents": [
    "99da10d2e1d2cdb08e4b84db93d681a154d56861"
  ],
  "author": {
    "name": "Johan Pas",
    "email": "j20012@outlook.com",
    "time": "Mon Dec 28 22:44:04 2015 +0100"
  },
  "committer": {
    "name": "Johan Pas",
    "email": "j20012@outlook.com",
    "time": "Mon Dec 28 23:54:23 2015 +0100"
  },
  "message": "Fix leak from tempest.conf in fake_config fixture\n\nThe config fixture used in Tempest unit tests\n(tests.fake_config.ConfigFixture) does not reset the\ncfg.CONF/config.CONF values when the test class is initialized.\nIf config.CONF already exists (e.g. with values from tempest.conf file\nthat have been retrieved during test discovery/load), then incorrect\nconfig settings might be used during a unit test.\n\nThere is a statement to (re)initialize cfg.CONF in the init of\ntests.fake_config.FakePrivate (this is a stub for\nconfig.TempestConfigPrivate). However if config.CONF already has\nattribute _config (of type TempestConfigPrivate), then\nTempestConfigPrivate is not called during the test (due to\nlogic in __getattr__ method in config.TempestConfigProxy class). So if\nconfig.CONF was created before start of the unit test, stub FakePrivate\nis not initialized and as a result cfg.CONF is not reset.\n\nThis patch moves the (re)initialization of cfg.CONF from FakePrivate to\nConfigFixture class to ensure that cfg.CONF/config.CONF reset is also\nexecuted if config.CONF already exists before start of the unit test.\n\nPartial-Bug: #1508815\n\nChange-Id: I9525628ffd263dd2ed3ad2411f24548dfd50f747\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ca8bc3e38d7e6b7784e1fbf1639dc2a74a512bb1",
      "old_mode": 33188,
      "old_path": "tempest/tests/fake_config.py",
      "new_id": "c45f6dae98d27534b58a9a0c694c1178a737a486",
      "new_mode": 33188,
      "new_path": "tempest/tests/fake_config.py"
    }
  ]
}