Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Nathan Rossi <nathan@nathanrossi.com>,
	Khem Raj <raj.khem@gmail.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH RESEND 2/2] glibc: ptest: Add support for running glibc test suite with ptest
Date: Wed, 13 Oct 2021 11:35:42 +0200	[thread overview]
Message-ID: <20211013113542.1c518bc7@ktm> (raw)
In-Reply-To: <e34be048ff6e037547bc7e0baf1c6d9f7d4e3e56.camel@linuxfoundation.org>

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

Hi Richard,

> On Wed, 2021-10-13 at 10:35 +0200, Lukasz Majewski wrote:
> > Dear Community,
> >   
> > > This patch introduces new recipe - namely 'glibc-tests', which
> > > builds and installs glibc test suite to OE/Yocto built image.
> > > 
> > > It reuses code from already available 'glibc-testsuite' recipe,
> > > which is run with 'bitbake glibc-testsuite -c check' and uses qemu
> > > to execute remotely (via SSH) tests on some emulated machine.
> > > 
> > > This recipe installs eligible tests on some rootfs image.
> > > Afterwards, either all of them or only time related subset, those
> > > tests can be executed on the real hardware, to facilitate
> > > validation of this platform with for example Y2038 problem
> > > compliance.
> > > 
> > > By default all tests are executed, with 'ptest-runner
> > > glibc-tests'. To test only time related subset - one needs to
> > > call: cd /usr/lib/glibc-tests/ptest/; rm run-ptest; \
> > > ln -s run-ptest-time run-ptest; cd -; ptest-runner glibc-tests
> > > 
> > > To facilitate debugging, source files are provided by default with
> > > the unstripped debugging symbols. Such approach would reduce the
> > > already complex recipe (as it inherits base glibc one), so there
> > > is no need to also install *-dbg and *-src packages.
> > >   
> > 
> > Gentle ping on this patch set.  
> 
> We're in the middle of trying to make a release. This change needs to
> wait until after that. We're starting to work through that backlog
> but easier things will go first.
>

Thanks for the update.
 
> FWIW I'm still very reticent to add in two code paths doing similar
> things so am not entirely sure we will be able to take this :(
> 

As fair as I understand those recipes (glibc related) - there are the
same binaries built once for the target machine.

Then those binaries are either run with QEMU or bundled into separate
package and then installed and run on a _real_ HW.

To even keep things more clear - I can just provide v2 of this patch,
which will only test time related API (as I do know that those
can be executed as standalone binaries) and state that it is meant for
Y2038 compliance testing.

> Cheers,
> 
> Richard
> 




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-10-13  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 10:43 [PATCH RESEND 1/2] glibc: Exclude common code to build tests to glibc-tests.inc Lukasz Majewski
2021-09-30 10:43 ` [PATCH RESEND 2/2] glibc: ptest: Add support for running glibc test suite with ptest Lukasz Majewski
2021-10-04 10:37   ` [OE-core] " Alexandre Belloni
2021-10-13  8:35   ` Lukasz Majewski
2021-10-13  8:45     ` Richard Purdie
2021-10-13  9:35       ` Lukasz Majewski [this message]
2021-10-13 10:01     ` [OE-core] " Alexandre Belloni

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