From: richard.purdie@linuxfoundation.org
To: Pgowda <pgowda.cve@gmail.com>, Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Randy MacLeod <rwmacleod@gmail.com>
Subject: Re: [OE-core] [PATCH] glibc: ptest: Add lib32-glibc-tests PROVIDES
Date: Fri, 13 May 2022 13:45:10 +0100 [thread overview]
Message-ID: <215dded4d396c69a484a5404d07499b45af819d0.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALY49869zPf6F8UELEue+9BvyToT=W=hGqSRtazXZW+zPO5c=A@mail.gmail.com>
On Fri, 2022-05-13 at 17:58 +0530, Pgowda wrote:
> Hi Luca,
>
> I have checked it again at my end and it seems to be working fine.
> The error is related to "setup NFS mount on target" and does not seem
> to be related to the patch.
> Can the patch be included again while running oe-selftest and checked?
No, it doesn't need to be checked again, it is breaking oe-selftest
when used to test target machine glibc.
The change in in the glibc ptest recipe and the failure is in
"glibc.GlibcSelfTestSystemEmulated.test_glibc" i.e. in the glibc tests
so there is a clear connection between these two things.
We need to work out why it breaks it and fix that. Running it again
doesn't help us at all.
What you really need is a way to replicate the failure. How did you
test this locally?
Cheers,
Richard
next prev parent reply other threads:[~2022-05-13 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 8:08 [PATCH] glibc: ptest: Add lib32-glibc-tests PROVIDES pgowda
2022-05-02 9:13 ` [OE-core] " Jose Quaresma
2022-05-02 20:30 ` Luca Ceresoli
2022-05-05 10:25 ` pgowda cve
2022-05-13 12:28 ` pgowda cve
2022-05-13 12:45 ` richard.purdie [this message]
2022-05-13 12:56 ` pgowda cve
2022-05-13 13:06 ` Randy MacLeod
2022-05-13 13:11 ` richard.purdie
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=215dded4d396c69a484a5404d07499b45af819d0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=rwmacleod@gmail.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