public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Lukasz Majewski <lukma@denx.de>
Cc: Nathan Rossi <nathan@nathanrossi.com>,
	Khem Raj <raj.khem@gmail.com>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [OE-core] [PATCH 2/2] glibc: ptest: Add support for running glibc test suite with ptest
Date: Thu, 26 Aug 2021 17:25:13 +0100	[thread overview]
Message-ID: <06310ae3618ccbb469ab025784da5b023704f2f7.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210826161212.12024b6b@ktm>

On Thu, 2021-08-26 at 16:12 +0200, Lukasz Majewski wrote:
> > On Thu, 2021-08-26 at 14:27 +0200, Lukasz Majewski wrote:
> > > 
> > > Do you have any more feedback regarding this patch?  
> > 
> > We're at feature freeze and this wasn't a planned change so it is too
> > late for this release cycle,
> 
> I see. Thanks for the update.
> 
> BTW: When one can expect the Yocto/poky would accept new patches again?
>
> 
> Honister is going to be released on October 2021 [1]. After this date
> this patch is going to be reconsidered?

I'd expect new development to start being looked at around the time of the
release, yes.

> > I'm struggling with the things that were
> > planned.
> 
> I can imagine that after the "override" change a lot of attention is
> necessary.
> 
> > 
> > I need to spend some time looking at what the other code is doing and
> > how we're using it on the autobuilder and whether we want to change
> > to use the ptest approach or not.
> 
> I see.
> 
> > 
> > I added Nathan Rossi to cc since he worked on the other code for this
> > and may have more insight.
> 
> I do hope that Nathan will provide some valuable input as well, as
> wrote the glibc-testsuite_%.bb recipe.

If you search the commits, e.g.:

http://git.yoctoproject.org/cgit.cgi/poky/log/?qt=grep&q=Rossi

you'll see he also worked on the gcc/binutils tests I mentioned.

Also, I'm not sure if you found them but these are run on our infrastructure
here:

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/3877/steps/19/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/3892/steps/20/logs/stdio

(one of the above uses user mode qemu iirc, the other uses system mode).

We then get reports like:

https://autobuilder.yocto.io/pub/non-release/20210825-18/testresults/testresult-report.txt

Cheers,

Richard




  reply	other threads:[~2021-08-26 16:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 15:08 [PATCH 1/2] glibc: Exclude common code to build tests to glibc-tests.inc ?ukasz Majewski
2021-08-23 15:08 ` [PATCH 2/2] glibc: ptest: Add support for running glibc test suite with ptest ?ukasz Majewski
2021-08-23 16:17   ` [OE-core] " Khem Raj
2021-08-23 18:24     ` ?ukasz Majewski
2021-08-23 19:52       ` Khem Raj
2021-08-23 20:09         ` ?ukasz Majewski
2021-08-23 20:41           ` Khem Raj
2021-08-24  7:36             ` ?ukasz Majewski
2021-08-24  7:41               ` Richard Purdie
2021-08-24  8:42                 ` ?ukasz Majewski
2021-08-26 12:27                   ` ?ukasz Majewski
2021-08-26 13:38                     ` Richard Purdie
2021-08-26 14:12                       ` ?ukasz Majewski
2021-08-26 16:25                         ` Richard Purdie [this message]
2021-08-27  7:52                       ` Nathan Rossi
2021-08-27  9:20                         ` ?ukasz Majewski
2021-08-27 11:29                           ` Nathan Rossi
2021-08-27 14:19                             ` ?ukasz Majewski

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=06310ae3618ccbb469ab025784da5b023704f2f7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=lukma@denx.de \
    --cc=nathan@nathanrossi.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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