From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: trini@konsulko.com, tuomas.tynkkynen@iki.fi, bmeng.cn@gmail.com,
jerome.forissier@arm.com, jserv@ccns.ncku.edu.tw,
eleanor15x@gmail.com, marscheng@google.com,
u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v2 5/6] test: 9p: Add test for 9P filesystem
Date: Thu, 24 Sep 2026 05:08:38 +0800 [thread overview]
Message-ID: <arQ_1vDTqU9d8uAT@google.com> (raw)
In-Reply-To: <CAFLszTimE0ZxNpYPjxDZdOQD4=ordEzcwgpnoGihYBN499edpg@mail.gmail.com>
On Fri, Sep 11, 2026 at 05:44:10AM -0600, Simon Glass wrote:
> Hi Kuan-Wei,
>
> On 2026-08-29T19:21:13, Kuan-Wei Chiu <visitorckw@gmail.com> wrote:
> > test: 9p: Add test for 9P filesystem
> >
> > Add automated pytest for the 9P filesystem testing directory listing
> > (ls) and file loading (load) over virtio-9p in QEMU ARM64. Also enable
> > the relevant configurations in qemu_arm64_defconfig.
> >
> > Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> >
> > configs/qemu_arm64_defconfig | 3 ++
> > test/py/tests/test_9p.py | 82 ++++++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 85 insertions(+)
>
> I think I saw a change to the hooks for this, so I assume it passes OK.
Yes. I tested with:
gitlab-ci-local --variable TEST_PY_TEST_SPEC=test_fs_9p "qemu_arm64 test.py"
>
> > diff --git a/test/py/tests/test_9p.py b/test/py/tests/test_9p.py
> > @@ -0,0 +1,82 @@
> > + output = ubman.run_command(f"load 9p rootfs {addr:x} /non_existent_file_9p.txt")
> > + assert "bytes read" not in output
> > +
> > + output = ubman.run_command("ls 9p invalid_tag /")
> > + assert test_file_name not in output
>
> Both negative cases pass for the wrong reason if the command silently
> produces no output. Please assert on the expected error string (e.g.
> 'Failed to load' / 'No such device') rather than the absence of a
> success token, so a future regression that swallows errors still fails
> the test.
>
Ack. Will do in v3.
Regards,
Kuan-Wei
next prev parent reply other threads:[~2026-09-23 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 19:21 [PATCH v2 0/6] fs: Add 9P filesystem support over virtio Kuan-Wei Chiu
2026-08-29 19:21 ` [PATCH v2 1/6] net: 9p: Add 9P2000.L protocol support Kuan-Wei Chiu
2026-09-11 11:43 ` Simon Glass
2026-08-29 19:21 ` [PATCH v2 2/6] fs: 9p: Add 9P filesystem support Kuan-Wei Chiu
2026-09-11 11:43 ` Simon Glass
2026-08-29 19:21 ` [PATCH v2 3/6] virtio: 9p: Add 9P transport driver Kuan-Wei Chiu
2026-09-11 11:43 ` Simon Glass
2026-09-23 20:53 ` Kuan-Wei Chiu
2026-08-29 19:21 ` [PATCH v2 4/6] doc: 9p: Add 9P filesystem documentation Kuan-Wei Chiu
2026-09-11 11:43 ` Simon Glass
2026-08-29 19:21 ` [PATCH v2 5/6] test: 9p: Add test for 9P filesystem Kuan-Wei Chiu
2026-09-11 11:44 ` Simon Glass
2026-09-23 21:08 ` Kuan-Wei Chiu [this message]
2026-09-15 15:57 ` Tom Rini
2026-08-29 19:21 ` [PATCH v2 6/6] MAINTAINERS: Add entry for 9PFS Kuan-Wei Chiu
2026-08-30 10:41 ` [PATCH v2 0/6] fs: Add 9P filesystem support over virtio Peter Robinson
2026-09-02 1:51 ` Kuan-Wei Chiu
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=arQ_1vDTqU9d8uAT@google.com \
--to=visitorckw@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=eleanor15x@gmail.com \
--cc=jerome.forissier@arm.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=marscheng@google.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=tuomas.tynkkynen@iki.fi \
--cc=u-boot@lists.u-boot-project.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