All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Pgowda <pgowda.cve@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
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 09:06:07 -0400	[thread overview]
Message-ID: <aeb5d0a1-de07-9c3f-d539-e641fd9ded41@windriver.com> (raw)
In-Reply-To: <CALY4984taQDm3GRxcJBCzGgHAt8jUP6fj8bD7cRe1FmjLkVoUQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2452 bytes --]

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-2https://almalinux.org/

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100

but that may also be incidental rather than required to see the error.

../Randy

>
> Thanks,
> Pgowda
>
> On Fri, May 13, 2022 at 6:15 PM<richard.purdie@linuxfoundation.org>  wrote:
>> 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
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#165559):https://lists.openembedded.org/g/openembedded-core/message/165559
>> Mute This Topic:https://lists.openembedded.org/mt/90831085/3616765
>> Group Owner:openembedded-core+owner@lists.openembedded.org
>> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub  [randy.macleod@windriver.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>

-- 
# Randy MacLeod
# Wind River Linux

[-- Attachment #2: Type: text/html, Size: 5025 bytes --]

  reply	other threads:[~2022-05-13 13:06 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 [this message]
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=aeb5d0a1-de07-9c3f-d539-e641fd9ded41@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pgowda.cve@gmail.com \
    --cc=richard.purdie@linuxfoundation.org \
    --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 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.