Lines Matching refs:we

46 tests in parallel we need to know which system resources are utilized by a
47 given test, as obviously we cannot run two tests that monopolize the same
48 resource. In some cases we would also need to partition the system resource
49 accordingly, e.g. if we have two memory stress tests running at the same time
50 we will need to cap each of these tests on half of the available memory, or
72 supposed to run, this means that we have to guess some upper limit on how long
74 for all testcases or whole suite or even larger. This means that we are wasting
75 time in the case that the test ends up stuck and we could have failed it much
78 supposed to crash a kernel under a minute is exported to the testrunner we can
85 runtest files. Once this system is in place we will have a list of all tests
86 along with their respective metadata - which means that we will be able to
89 In order to achieve this we need two things:
92 Then we could define groups of tests based on that. I.e. instead of having
93 syscall runtest file we would ask the testrunner to run all test that have a
96 Secondly we will have to store the test variants in the test metadata instead
101 * To run CVE related test we would select testcases with CVE tag
103 * To run IPC test we will define a list of IPC syscalls and run all syscall
241   we put all of them there?
246 So far this proof of concept generates a metadata file. I guess that we need