From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Yan Xin Kuan" <yanxk.fnst@fujitsu.com>
Cc: <openembedded-core@lists.openembedded.org>,
<fnstml-fujitsuten@fujitsu.com>
Subject: Re: [OE-core] [meta-oe][PATCH V1] cpio: add ptest
Date: Tue, 7 Feb 2023 18:26:27 +0100 [thread overview]
Message-ID: <20230207182627.0ad409cc@booty> (raw)
In-Reply-To: <1667352933-9298-1-git-send-email-yanxk.fnst@fujitsu.com>
Hello Yan,
On Wed, 2 Nov 2022 09:35:33 +0800
^^^^^^^^^^
Not sure where this data comes from... :)
"Yan Xin Kuan" <yanxk.fnst@fujitsu.com> wrote:
> From: Yan <yanxk.fnst@fujitsu.com>
>
> enable the ptest function for cpio.
>
> cpio takes 1 second maybe less, so it is fast.
>
> you will get ptest result like this:
>
> PASS: symlink
> SKIP: symlink-bad-length
> ......
>
> Signed-off-by: Yan <yanxk.fnst@fujitsu.com>
Autobuilder testing with this patch generated lots of warnings:
WARNING: cpio-2.13-r0 do_package_qa: QA Issue: File
/usr/lib/cpio/ptest/tests/atconfig in package cpio-ptest contains reference to TMPDIR
Here are a few logs:
https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/4375/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/6685/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/104/builds/5526/steps/12/logs/stdio
More at:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4894
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-02-07 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 1:35 [meta-oe][PATCH V1] cpio: add ptest yanxk.fnst
2023-02-07 17:26 ` Luca Ceresoli [this message]
[not found] ` <17419AD8D8969177.20960@lists.openembedded.org>
2023-02-07 17:43 ` [OE-core] " Luca Ceresoli
2023-02-07 23:39 ` 回复: " yanxk.fnst
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=20230207182627.0ad409cc@booty \
--to=luca.ceresoli@bootlin.com \
--cc=fnstml-fujitsuten@fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yanxk.fnst@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.