From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jhonata Poma-Hansen" <jhonata.poma@gmail.com>,
<openembedded-core@lists.openembedded.org>
Cc: "Yi Zhao" <yi.zhao@windriver.com>,
"Ross Burton" <ross.burton@arm.com>,
"Richard Purdie" <richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH v4] rsync: add ptest support
Date: Tue, 05 May 2026 09:54:00 +0200 [thread overview]
Message-ID: <DIAKXED37M90.4QX504G4C9DW@bootlin.com> (raw)
In-Reply-To: <20260429-b4-yocto-16211-v4-v4-1-211f27c4daea@gmail.com>
On Wed Apr 29, 2026 at 4:26 PM CEST, Jhonata Poma-Hansen wrote:
> Wire up upstream's runtests.sh testsuite as a ptest package. The
> testsuite runs rsync itself through 43 .test scenarios covering
> ACLs, xattrs, device nodes, hardlinks, symlinks, daemon mode,
> filters, backup, batch, etc., plus 3 CHECK_SYMLINKS variants
> (chown-fake, devices-fake, xattrs-hlink).
Hi Jhonata,
Thanks for the new version.
It works correctly with the current version of rsync, but we still have
a small issue, sorry.
It looks like with the version 3.4.2, the runtests.sh file was removed
and a runtests.py one was introduced. We already have a patch on the
mailing list upgrading the rsync recipe [1]. Can you rebase on it and
make sure to use the new test script?
[1]: https://lists.openembedded.org/g/openembedded-core/message/236364
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-05-05 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 11:30 [PATCH v3] rsync: add ptest support Jhonata Poma-Hansen
2026-04-23 11:40 ` jhonata.poma
2026-04-24 11:33 ` [OE-core] " Mathieu Dubois-Briand
2026-04-30 14:25 ` Jhonata Poma-Hansen
2026-04-29 14:26 ` [PATCH v4] " Jhonata Poma-Hansen
2026-04-29 14:27 ` [PATCH v3] " Jhonata Poma-Hansen
2026-05-05 7:54 ` Mathieu Dubois-Briand [this message]
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=DIAKXED37M90.4QX504G4C9DW@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=jhonata.poma@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--cc=yi.zhao@windriver.com \
/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