Home
last modified time | relevance | path

Searched refs:verify (Results 1 – 8 of 8) sorted by relevance

/tools/testing/selftests/sysctl/
Dsysctl.sh177 verify() function
236 if ! verify "${TEST_FILE}"; then
244 if verify "${TARGET}"; then
253 if ! verify "${TARGET}"; then
262 if verify "${TARGET}"; then
276 if ! verify "${TARGET}"; then
286 if ! verify "${TARGET}"; then
296 if verify "${TARGET}"; then
307 if verify "${TARGET}"; then
379 if ! verify "${TARGET}"; then
[all …]
/tools/testing/selftests/livepatch/
DREADME7 The test suite loads and unloads several test kernel modules to verify
/tools/iio/
Diio_utils.c649 int verify) in _write_sysfs_int() argument
683 if (verify) { in _write_sysfs_int()
746 const char *val, int verify) in _write_sysfs_string() argument
781 if (verify) { in _write_sysfs_string()
/tools/testing/selftests/rcutorture/doc/
Dinitrd.txt17 # Manually verify that initrd contains needed binaries and libraries.
/tools/testing/selftests/tc-testing/creating-plugins/
DAddingPlugins.txt21 verify
80 'verify'
/tools/testing/selftests/tc-testing/
DREADME83 - verify
90 success, but do not otherwise verify the results.
92 The execute and verify stages each run one command. The execute stage
94 verify stage checks the return code for success, and also compares
218 - verify
/tools/testing/selftests/android/ion/
DREADME8 This is a test utility to verify ION buffer sharing in user space
/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt55 verifyCmd: The tc command to be run to verify successful execution.