From: richard.purdie@linuxfoundation.org
To: Randy MacLeod <randy.macleod@windriver.com>,
Pgowda <pgowda.cve@gmail.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>,
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 14:11:18 +0100 [thread overview]
Message-ID: <9297a0be88bd4efbb2c08cf6056d460bf2442f22.camel@linuxfoundation.org> (raw)
In-Reply-To: <aeb5d0a1-de07-9c3f-d539-e641fd9ded41@windriver.com>
On Fri, 2022-05-13 at 09:06 -0400, Randy MacLeod wrote:
> On 2022-05-13 08:56, Pgowda wrote:
>
> > Hi Richard,
> >
> > Thanks for the confirmation.
> >
> >
> > > What you really need is a way to replicate the failure. How did
> > > you
> > > test this locally?
> > I ran the complete Oe-selftest suite with the latest poky sources
> > after applying the patch:-
> > oe-selftest -a -t machine -t toolchain-system
> >
> > Can you please let me know if I have to export any specific
> > environment to replicate the failure?
> Please explain what changes you made to you local.conf
> if any.
> The only one that stands out to me in:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100
> is :
> INHERIT += 'testimage'
> but perhaps that's done automatically for:
> oe-selftest -a -t machine -t toolchain-system
> Also, what host distro did you use?
> The failure happened on an alma distro: worker = alma8-ty-2
> https://almalinux.org/
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100
>
> but that may also be incidental rather than required to see the
> error.
>
>
Also, going back to the original patch being tested here, why is it
needed? What are you doing to reproduce that failure?
I'm guessing you have to have enabled multilibs? Do we expect that to
work with the glibc tests?
Cheers,
Richard
prev parent reply other threads:[~2022-05-13 13:11 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
2022-05-13 12:56 ` pgowda cve
2022-05-13 13:06 ` Randy MacLeod
2022-05-13 13:11 ` richard.purdie [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=9297a0be88bd4efbb2c08cf6056d460bf2442f22.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=randy.macleod@windriver.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