diff options
| author |   Benjamin Gray <bgray@linux.ibm.com> | 2023-07-25 10:58:39 +1000 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2023-08-02 22:22:19 +1000 |
| commit | 68877ff20a7f4f773069784cfe4f6fe9c7b9a841 (patch) | |
| tree | ed3e75c33d80cb5f0c115d71d1d26d4b3fba8d88 /tools/testing/selftests/powerpc/ptrace/ptrace-hwbreak.c | |
| parent | powerpc: Explicitly include correct DT includes (diff) | |
| download | wireguard-linux-68877ff20a7f4f773069784cfe4f6fe9c7b9a841.tar.xz wireguard-linux-68877ff20a7f4f773069784cfe4f6fe9c7b9a841.zip | |
selftests/powerpc/ptrace: Explain why tests are skipped
Many tests require specific hardware features/configurations that a
typical machine might not have. As a result, it's common to see a test
is skipped. But it is tedious to find out why a test is skipped
when all it gives is the file location of the skip macro.
Convert SKIP_IF() to SKIP_IF_MSG(), with appropriate descriptions of why
the test is being skipped. This gives a general idea of why a test is
skipped, which can be looked into further if it doesn't make sense.
Signed-off-by: Benjamin Gray <bgray@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230725005841.28854-3-bgray@linux.ibm.com
Diffstat (limited to 'tools/testing/selftests/powerpc/ptrace/ptrace-hwbreak.c')
| -rw-r--r-- | tools/testing/selftests/powerpc/ptrace/ptrace-hwbreak.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/selftests/powerpc/ptrace/ptrace-hwbreak.c b/tools/testing/selftests/powerpc/ptrace/ptrace-hwbreak.c index 1345e9b9af0f..a16239277a6f 100644 --- a/tools/testing/selftests/powerpc/ptrace/ptrace-hwbreak.c +++ b/tools/testing/selftests/powerpc/ptrace/ptrace-hwbreak.c @@ -603,7 +603,7 @@ static int ptrace_hwbreak(void) wait(NULL); get_dbginfo(child_pid, &dbginfo); - SKIP_IF(dbginfo.num_data_bps == 0); + SKIP_IF_MSG(dbginfo.num_data_bps == 0, "No data breakpoints present"); dawr = dawr_present(&dbginfo); run_tests(child_pid, &dbginfo, dawr); |