diff options
| author | aszlig <aszlig@redmoonstudios.org> | 2016-05-06 16:06:22 +0200 |
|---|---|---|
| committer | aszlig <aszlig@redmoonstudios.org> | 2016-05-06 16:56:43 +0200 |
| commit | 4f796c28d57887cc9812190bc99fb45b2acd6d1c (patch) | |
| tree | 4ecf8e8f43213bb9d232352f086c01b10a06a3c2 /pkgs/development/python-modules/GitPython/hardcode-git-path.patch | |
| parent | dc6d0030110d0ebd7f13a0fdaccfe494fbad0e29 (diff) | |
nixos/tests: Add a test for boot stage 1
We already have a small regression test for #15226 within the swraid
installer test. Unfortunately, we only check there whether the md
kthread got signalled but not whether other rampaging processes are
still alive that *should* have been killed.
So in order to do this we provide multiple canary processes which are
checked after the system has booted up:
* canary1: It's a simple forking daemon which just sleeps until it's
going to be killed. Of course we expect this process to not
be alive anymore after boot up.
* canary2: Similar to canary1, but tries to mimick a kthread to make
sure that it's going to be properly killed at the end of
stage 1.
* canary3: Like canary2, but this time using a @ in front of its
command name to actually prevent it from being killed.
* kcanary: This one is a real kthread and it runs until killed, which
shouldn't be the case.
Tested with and without 67223ee and everything works as expected, at
least on my machine.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions
