mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-07-11 12:25:52 +00:00
6ae53a1509
The 'commandhelper' checks effectively whether the parent process is still around to report whether it was daemonized or not. This creates a unlikely race condition in cases when we do actually daemonize the process as the intermediate process used for the daemonization might not have terminated yet which would report wrong result leading to test failure. For now there's just 'test4' which actually daemonizes the process. Add an argument '--check-daemonize' which asks for retries of the daemonization check in cases where we expect that the commandhelper is going to be daemonized and use it in 'test4' to make the test more reliable. I've observed the test failure sporadically when my box is under load e.g. while building two trees at once. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> |
||
|---|---|---|
| .. | ||
| test2.log | ||
| test3.log | ||
| test4.log | ||
| test5.log | ||
| test6.log | ||
| test7.log | ||
| test8.log | ||
| test9.log | ||
| test10.log | ||
| test11.log | ||
| test12.log | ||
| test13.log | ||
| test14.log | ||
| test15.log | ||
| test16.log | ||
| test20.log | ||
| test21.log | ||
| test26.log | ||
| test27.log | ||