)]}'
{
  "commit": "dff5762567aa78c935ad20d59bf652970ac2572e",
  "tree": "180295f22b30eaf0d5338439d403de8eaea723d8",
  "parents": [
    "4691c75e144d6e30576eed02bea857acb47e9535",
    "189e57b97df2fc416027ec44bb19ea427958f411"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Tue Mar 24 21:33:50 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Mar 24 21:33:50 2020 +0000"
  },
  "message": "Merge #158\n\n158: Create test runner to run integration tests in qemu r\u003dtorfmaster a\u003dtorfmaster\n\nThis PR proposes a test runner written in rust. The goal is to have the following improvements over the previous solution using single a command line call:\r\n\r\n * it should time out transparently and signal that it has timed out\r\n * it should note that tests failed\r\n * it shouldn\u0027t be too fragile (e.g. changing output from the kernel should not break the test)\r\n * it should note that test were not executed\r\n\r\nCurrently the code is a PoC and for example the tests in the example crate and in this crate could be connected so that the information which tests exist isn\u0027t duplicated (and tests are not forgotten).\r\n\r\nI\u0027m just gathering hints what a robust test runner could look like so any feedback is welcome!\n\nCo-authored-by: torfmaster \u003cbriefe@kebes.de\u003e\n",
  "tree_diff": []
}