tree 88850260298fe6029158eb846a41e8f90cb4202d
parent 80f2a1f56f364e58b9cf6e1d110587a42e8993eb
parent 672b543c073f7d1e5816978afea5ff13525d4d64
author bors[bot] <26634292+bors[bot]@users.noreply.github.com> 1581690609 +0000
committer GitHub <noreply@github.com> 1581690609 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJeRq7xCRBK7hj4Ov3rIwAAdHIIAJRMvEtE0G6tpKEzMFkJs89C
 g3tIAr28OZSvzF1Gv9wsKDN5us+lsfyuLEe2WyMLF6mnDJL04T5OQm1WmYyVsvfR
 PYAcUI75kSABNdHd+kvMPXmPJUz7AlLSMVyhvYZxHQzSlPe+dHV/Z3yRkNySxNg7
 yTkywZ+hozEOSg4f/Vee40L2hB1+EfyWjY3tvqWCeN8otihzUb0nH2rMUuDr/Fo7
 +R6e/mitvTn2ltbcJDZMYs3lR7YA0EF4V8we2mjK7Vd8DhnYo+XzpCtEN0HX6dpx
 uTZfd161Mxq0sNaNrIxnLEiouV4TsjXzFHSOwYZSxMwlTxjoYwTGjfv0dnAUiXI=
 =NkWb
 -----END PGP SIGNATURE-----
 

Merge #136

136: Create syscall recorder for tests r=Woyten a=torfmaster

# Content of the PR

This 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.  

# Help needed

Comments 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

 * test the set alarm retry mechanism of the alarm implementation
 * test non-trivial callbacks (i.e. temperature)

Co-authored-by: torfmaster <briefe@kebes.de>