Searched refs:failures (Results 1 – 10 of 10) sorted by relevance
| /tools/testing/selftests/vm/ |
| D | mremap_test.c | 262 static void run_mremap_test_case(struct test test_case, int *failures, in run_mremap_test_case() argument
275 *failures += 1; in run_mremap_test_case()
335 int failures = 0; in main() local
413 run_mremap_test_case(test_cases[i], &failures, threshold_mb, in main()
420 run_mremap_test_case(perf_test_cases[i], &failures, in main()
424 if (failures > 0) in main()
|
| /tools/testing/selftests/rcutorture/bin/ |
| D | kvm-check-branches.sh | 102 echo '!!! ' $nfail failures in $ntry 'runs!!!'
105 echo No failures in $ntry runs.
|
| D | torture.sh | 245 touch $T/failures
279 echo "$curflavor($retcode)" $resdir >> $T/failures
334 echo "allmodconfig($retcode)" $amcdir >> $T/failures
418 nfailures="`wc -l "$T/failures" | awk '{ print $1 }'`"
|
| /tools/testing/fault-injection/ |
| D | failcmd.sh | 31 specifies how many times failures may happen at most.
59 inject slab allocation failures
61 inject page allocation failures
|
| /tools/testing/selftests/net/ |
| D | rxtimestamp.c | 361 int failures = 0; in main() local
420 failures++; in main()
424 failures++; in main()
427 if (!failures) in main()
429 return failures; in main()
|
| /tools/testing/ktest/examples/include/ |
| D | defaults.conf | 151 STORE_FAILURES = ${THIS_DIR}/failures
|
| /tools/testing/selftests/bpf/ |
| D | README.rst | 41 Additional information about selftest failures are
44 profiler[23] test failures with clang/llvm <12.0.0
83 bpf_iter test failures with clang/llvm 10.0.0
169 old to support them, they shouldn't cause build failures or runtime test
170 failures:
|
| /tools/testing/selftests/drivers/net/mlxsw/ |
| D | qos_lib.sh | 68 the other. That will cause spurious failures (or,
|
| /tools/testing/selftests/x86/ |
| D | ldt_gdt.c | 534 int failures = 0, iters = 5, i; in do_multicpu_tests() local
608 failures++; in do_multicpu_tests()
618 if (failures) { in do_multicpu_tests()
619 printf("[FAIL]\t%d of %d iterations failed\n", failures, iters); in do_multicpu_tests()
|
| /tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 84 Repeated failures of the setup/teardown may indicate a problem with the test
|