)]}'
{
  "commit": "2617eb6bd07caa91a6f2ed7a2874f69d1e77d432",
  "tree": "79903ed2f59417729b6e44b2fe041d80d868efad",
  "parents": [
    "cea8c5fb333638da7405b0aa698894955c4d884c"
  ],
  "author": {
    "name": "Rich Lane",
    "email": "rlane@bigswitch.com",
    "time": "Tue May 05 14:19:59 2015 -0700"
  },
  "committer": {
    "name": "Rich Lane",
    "email": "rlane@bigswitch.com",
    "time": "Tue May 05 14:19:59 2015 -0700"
  },
  "message": "tests: add sleep after flow timeouts\n\nFor normal flow-mods we can use the barrier message to find out when the change\nhas made it to the datapath. This isn\u0027t the case with timeouts, because the\nupdate isn\u0027t associated with any controller connection. When tests are run in\nshort succession the timed out flow may still exist in the datapath when the\nnext test starts.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a32251d47c1ac19d9d3d225e656f7ee9a857983d",
      "old_mode": 33188,
      "old_path": "tests/detailed_contr_sw_messages.py",
      "new_id": "824692fd3b63bf291da32a2acecd2434c68269a2",
      "new_mode": 33188,
      "new_path": "tests/detailed_contr_sw_messages.py"
    },
    {
      "type": "modify",
      "old_id": "0467e4bd3c6d2968ca769fed8ac18b87bb53253c",
      "old_mode": 33188,
      "old_path": "tests/flow_expire.py",
      "new_id": "ccbad2068acbc9633f8c33533d85f12db495aafb",
      "new_mode": 33188,
      "new_path": "tests/flow_expire.py"
    }
  ]
}