public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <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>,
	"Jhonata Poma-Hansen" <jhonata.poma@gmail.com>
Subject: Re: [OE-core] [PATCH v3] rsync: add ptest support
Date: Fri, 24 Apr 2026 13:33:40 +0200	[thread overview]
Message-ID: <DI1CPLA12N5H.16XL7T8INAAJ6@bootlin.com> (raw)
In-Reply-To: <20260423113024.2549245-1-jhonata.poma@gmail.com>

On Thu Apr 23, 2026 at 1:30 PM CEST, Jhonata Poma-Hansen via lists.openembedded.org 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).
>
> Signed-off-by: Jhonata Poma-Hansen <jhonata.poma@gmail.com>
> ---

Hi Jhonata,

Thanks for adding tests.

It looks like this is failing on the autobuilder, riscv64 machine. This
might be due to timings, as these machines tend to be slower.

AssertionError:
Failed ptests:
{'rsync': ['hardlinks']}

https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1505

Additional logs can be found here:
https://valkyrie.yocto.io/pub/non-release/20260424-40/testresults/qemuriscv64-ptest/core-image-ptest-rsync/

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      parent reply	other threads:[~2026-04-24 11:34 UTC|newest]

Thread overview: 3+ 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 ` 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=DI1CPLA12N5H.16XL7T8INAAJ6@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