)]}'
{
  "commit": "bc3f349c6298fda596f4df6b778e6d6a025139bf",
  "tree": "88850260298fe6029158eb846a41e8f90cb4202d",
  "parents": [
    "80f2a1f56f364e58b9cf6e1d110587a42e8993eb",
    "672b543c073f7d1e5816978afea5ff13525d4d64"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Fri Feb 14 14:30:09 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Feb 14 14:30:09 2020 +0000"
  },
  "message": "Merge #136\n\n136: Create syscall recorder for tests r\u003dWoyten a\u003dtorfmaster\n\n# Content of the PR\r\n\r\nThis PR contains an \"event recorder\" which enables to write unit tests which invoke syscalls. The idea is to capture all syscalls and record them to assert which syscalls occur. The return value for a syscall can also be set.  \r\n\r\n# Help needed\r\n\r\nComments are very welcome. The mock syscall implementation is very crude because it is good enough to cover the only existing test case. Ideas for meaningful tests are very welcome so I can elaborate which infrastructure is needed to create these tests. Ideas would be\r\n\r\n * test the set alarm retry mechanism of the alarm implementation\r\n * test non-trivial callbacks (i.e. temperature)\n\nCo-authored-by: torfmaster \u003cbriefe@kebes.de\u003e\n",
  "tree_diff": []
}