Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
	<openembedded-core@lists.openembedded.org>
Cc: <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH v2] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures
Date: Fri, 24 Jul 2026 19:44:54 +0200	[thread overview]
Message-ID: <DK6ZLE8Z4WZG.3VXZXP49YQWE0@bootlin.com> (raw)
In-Reply-To: <20260720125854.39562-1-pratik.farkase@est.tech>

On Mon Jul 20, 2026 at 2:58 PM CEST, Pratik Farkase wrote:
> The bsdcpio_test odc/newc format tests verify archive headers byte-by-byte
> including inode and device numbers. On ext4 root filesystems (particularly
> qemuarm64 and qemuriscv64) inode numbers can exceed the odc 6-octal-digit
> or newc 8-hex-digit field widths, causing intermittent assertion failures
> in test_format_newc and test_option_c.
>
> Run all tests from a tmpfs working directory where inode numbers always
> start small, avoiding the overflow condition.
>
> [YOCTO #16231] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16231
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---

Hi Pratik,

Thanks for the new version. It looks like we have some ptest failures
here:

Failed ptests:
{'libarchive': ['libarchive_test',
                'bsdtar_test',
                'bsdcpio_test',
                'bsdcat_test',
                'bsdunzip_test']}

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4107
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4091
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1981

Can you have a look at the issue?

Thanks,
Mathieu

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



      reply	other threads:[~2026-07-24 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 12:26 [OE-core][PATCH v1] libarchive: ptest: run tests from tmpfs to avoid inode overflow failures Pratik Farkase
2026-07-20 12:39 ` Paul Barker
2026-07-20 13:05   ` Pratik Farkase
     [not found]   ` <18C401467A678464.1234146@lists.openembedded.org>
2026-07-20 14:00     ` Pratik Farkase
2026-07-20 12:58 ` [OE-core][PATCH v2] " Pratik Farkase
2026-07-24 17:44   ` 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=DK6ZLE8Z4WZG.3VXZXP49YQWE0@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pratik.farkase@ericsson.com \
    --cc=pratik.farkase@est.tech \
    /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