Searched hist:"7 dd4d225" (Results 1 – 4 of 4) sorted by relevance
/reactos/modules/rostests/rosautotest/ |
H A D | CPipe.h | diff 7dd4d225 Tue Apr 23 07:17:05 GMT 2019 Colin Finck <colin@reactos.org> [ROSAUTOTEST] Implement a process activity timeout of 2 minutes. If there is no log output within 2 minutes, the test process is killed, and we continue with the next test.
This is a rather graceful approach compared to sysreg2's 3 minute timeout before killing and restarting the entire VM. Since we added autochk for FAT filesystems, the filesystem is often "fixed" after a reset with the consequence that ReactOS doesn't boot up anymore. The sysreg2 restart code still remains for handling tests causing BSODs.
|
H A D | CPipe.cpp | diff 7dd4d225 Tue Apr 23 07:17:05 GMT 2019 Colin Finck <colin@reactos.org> [ROSAUTOTEST] Implement a process activity timeout of 2 minutes. If there is no log output within 2 minutes, the test process is killed, and we continue with the next test.
This is a rather graceful approach compared to sysreg2's 3 minute timeout before killing and restarting the entire VM. Since we added autochk for FAT filesystems, the filesystem is often "fixed" after a reset with the consequence that ReactOS doesn't boot up anymore. The sysreg2 restart code still remains for handling tests causing BSODs.
|
H A D | CProcess.cpp | diff 7dd4d225 Tue Apr 23 07:17:05 GMT 2019 Colin Finck <colin@reactos.org> [ROSAUTOTEST] Implement a process activity timeout of 2 minutes. If there is no log output within 2 minutes, the test process is killed, and we continue with the next test.
This is a rather graceful approach compared to sysreg2's 3 minute timeout before killing and restarting the entire VM. Since we added autochk for FAT filesystems, the filesystem is often "fixed" after a reset with the consequence that ReactOS doesn't boot up anymore. The sysreg2 restart code still remains for handling tests causing BSODs.
|
H A D | CWineTest.cpp | diff 7dd4d225 Tue Apr 23 07:17:05 GMT 2019 Colin Finck <colin@reactos.org> [ROSAUTOTEST] Implement a process activity timeout of 2 minutes. If there is no log output within 2 minutes, the test process is killed, and we continue with the next test.
This is a rather graceful approach compared to sysreg2's 3 minute timeout before killing and restarting the entire VM. Since we added autochk for FAT filesystems, the filesystem is often "fixed" after a reset with the consequence that ReactOS doesn't boot up anymore. The sysreg2 restart code still remains for handling tests causing BSODs.
|