From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Gustavo Romero" <gustavo.romero@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [RFC PATCH-for-10.2? v2] tests/tcg: Skip syscall catchpoint test if pipe2() syscall not available
Date: Tue, 9 Dec 2025 14:10:06 -0600 [thread overview]
Message-ID: <dd11ee38-13dd-4626-9a84-aff23bfdf365@linaro.org> (raw)
In-Reply-To: <eee34d92-3c8d-4ae9-93fc-66bff89d279f@linaro.org>
On 12/9/25 13:26, Philippe Mathieu-Daudé wrote:
> ping?
>
> On 3/12/25 15:37, Philippe Mathieu-Daudé wrote:
>> Avoid the following errors testing i386 and ppc64:
>>
>> $ make check-tcg
>> ...
>> TEST hitting a syscall catchpoint on i386
>> warning: File transfers from remote targets can be slow. Use "set sysroot" to access
>> files locally instead.
>> Traceback (most recent call last):
>> File "tests/tcg/multiarch/gdbstub/catch-syscalls.py", line 53, in <module>
>> main(run_test)
>> File "tests/guest-debug/test_gdbstub.py", line 53, in main
>> test()
>> File "tests/tcg/multiarch/gdbstub/catch-syscalls.py", line 22, in run_test
>> gdb.execute("catch syscall pipe2 read")
>> gdb.error: Unknown syscall name 'pipe2'.
>> qemu-i386: QEMU: Terminated via GDBstub
>> ...
>> TEST hitting a syscall catchpoint on ppc64
>> warning: File transfers from remote targets can be slow. Use "set sysroot" to access
>> files locally instead.
>> Traceback (most recent call last):
>> File "tests/tcg/multiarch/gdbstub/catch-syscalls.py", line 53, in <module>
>> main(run_test)
>> File "tests/guest-debug/test_gdbstub.py", line 53, in main
>> test()
>> File "tests/tcg/multiarch/gdbstub/catch-syscalls.py", line 22, in run_test
>> gdb.execute("catch syscall pipe2 read")
>> gdb.error: Unknown syscall name 'pipe2'.
>> qemu-ppc64: QEMU: Terminated via GDBstub
>> ...
>> TEST hitting a syscall catchpoint on ppc64le
>> warning: File transfers from remote targets can be slow. Use "set sysroot" to access
>> files locally instead.
>> Traceback (most recent call last):
>> File "tests/tcg/multiarch/gdbstub/catch-syscalls.py", line 53, in <module>
>> main(run_test)
>> File "tests/guest-debug/test_gdbstub.py", line 53, in main
>> test()
>> File "tests/tcg/multiarch/gdbstub/catch-syscalls.py", line 22, in run_test
>> gdb.execute("catch syscall pipe2 read")
>> gdb.error: Unknown syscall name 'pipe2'.
>> qemu-ppc64le: QEMU: Terminated via GDBstub
>> make: Target 'check-tcg' not remade because of errors.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> RFC because I have no clue whether SYS_pipe2 should be present
>> on these targets, I just want the CI to pass full green.
>>
>> v2: Drop extraneous 'if'
>> ---
>> tests/tcg/multiarch/gdbstub/catch-syscalls.py | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/tcg/multiarch/gdbstub/catch-syscalls.py b/tests/tcg/multiarch/
>> gdbstub/catch-syscalls.py
>> index ccce35902fb..79c8d532d1f 100644
>> --- a/tests/tcg/multiarch/gdbstub/catch-syscalls.py
>> +++ b/tests/tcg/multiarch/gdbstub/catch-syscalls.py
>> @@ -22,7 +22,8 @@ def run_test():
>> gdb.execute("catch syscall pipe2 read")
>> except gdb.error as exc:
>> exc_str = str(exc)
>> - if "not supported on this architecture" in exc_str:
>> + if "not supported on this architecture" in exc_str \
>> + or "Unknown syscall name 'pipe2'" in exc_str:
>> print("SKIP: {}".format(exc_str))
>> return
>> raise
>
>
Seems reasonable.
Acked-by: Richard Henderson <richard.henderson@linaro.org>
r~
s
next prev parent reply other threads:[~2025-12-09 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 14:37 [RFC PATCH-for-10.2? v2] tests/tcg: Skip syscall catchpoint test if pipe2() syscall not available Philippe Mathieu-Daudé
2025-12-09 19:26 ` Philippe Mathieu-Daudé
2025-12-09 20:10 ` Richard Henderson [this message]
2025-12-09 20:49 ` Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd11ee38-13dd-4626-9a84-aff23bfdf365@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=laurent@vivier.eu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).