![]() | |||||||||||||
Messages in this thread |
Hi! > > SGI would like to announce the Linux Test Project. The goal of this > > project is to create a formalized test system for the Linux kernel. > > > > We have released a set of 96 tests on the project's website > > (http://oss.sgi.com/projects/ltp/). These tests exercise file systems > > and system calls and can be used for stress testing or sanity tests. > > > > One question: how is the framework going to handle tests which cause > pathological behavior in the kernel. For example, 'infinite' hangs in > the MM system during OOM, or crashes (OOPSes, panics) or deadlocks > (process stuck in 'D' state). Most often these are the results of the > tests I tend to run. > Any testbed needs to handle these situations, at least somewhat. For > example, if I leave a 12 hour regression going and leave the console, > and I come back to see the system has rebooted itself, or is stuck solid > - how do I know which test has 'failed'? You can always run the tests in user-mode-linux to see if that crashed... Pavel -- I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:58 [from the cache] ©2003-2008 | |||||||||||||