Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Khem Raj <raj.khem@gmail.com>
Cc: Nathan Rossi <nathan@nathanrossi.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Lee Chee Yang <chee.yang.lee@intel.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v4] glibc: ptest: Add running glibc time related test suite (Y2038) with ptest
Date: Fri, 12 Nov 2021 09:48:42 +0100	[thread overview]
Message-ID: <20211112094842.1a636a88@ktm> (raw)
In-Reply-To: <023667d47dfa5b3e08858b06596d15986cdc26c2.camel@linuxfoundation.org>

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

Hi Richard, Khem

> On Thu, 2021-11-11 at 05:51 -0800, Khem Raj wrote:
> > On Tue, Nov 9, 2021 at 7:29 AM Lukasz Majewski <lukma@denx.de>
> > wrote:  
> > > 
> > > This patch introduces new recipe - namely 'glibc-tests', which
> > > builds and installs time related (to check if Y2038 support
> > > works) 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 time related glibc tests on some rootfs
> > > image. Afterwards, those tests can be executed on the real
> > > hardware, to facilitate validation of it with Y2038 problem
> > > compliance.
> > > 
> > > To test time related subset - one needs to call:
> > > ptest-runner glibc-tests
> > > then change the date after Y2038 threshold for 32 bit systems:
> > > date -s "20 JAN 2038 18:00:00"
> > > and then run ptest-runner again.
> > > 
> > > 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.
> > > 
> > > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > > 
> > > ---
> > > Changes for v4:
> > > - Add entry for 'glibc-tests' in the maintainers.inc file
> > > - Remove nativesdk from BBCLASSEXTEND as this resipe is not
> > > supposed to be the part of SDK
> > > 
> > > Changes for v3:
> > > - Provide missing ${PN}-ptest for PACKAGES, PROVIDES and
> > >   RPROVIDES variables
> > > 
> > > Changes for v2:
> > > - Just focus on time related set of tests as those can be run as
> > >   standalone
> > > - Reuse of already built tests (from glibc-tests.inc) and depoloy
> > >   them on the HW target.
> > > - Provide single 'run-ptest' script.
> > > - Update the recipe to run with newest poky's -master
> > > ---
> > >  meta/conf/distro/include/maintainers.inc      |   1 +
> > >  .../distro/include/ptest-packagelists.inc     |   1 +
> > >  meta/recipes-core/glibc/glibc-tests_2.34.bb   | 113
> > > ++++++++++++++++++ meta/recipes-core/glibc/glibc/run-ptest
> > > |  37 ++++++ 4 files changed, 152 insertions(+)
> > >  create mode 100644 meta/recipes-core/glibc/glibc-tests_2.34.bb
> > >  create mode 100755 meta/recipes-core/glibc/glibc/run-ptest
> > > 
> > > diff --git a/meta/conf/distro/include/maintainers.inc
> > > b/meta/conf/distro/include/maintainers.inc index
> > > baec2bef4d..7104e091fc 100644 ---
> > > a/meta/conf/distro/include/maintainers.inc +++
> > > b/meta/conf/distro/include/maintainers.inc @@ -209,6 +209,7 @@
> > > RECIPE_MAINTAINER:pn-glibc = "Khem Raj <raj.khem@gmail.com>"
> > > RECIPE_MAINTAINER:pn-glibc-locale = "Khem Raj
> > > <raj.khem@gmail.com>" RECIPE_MAINTAINER:pn-glibc-mtrace = "Khem
> > > Raj <raj.khem@gmail.com>" RECIPE_MAINTAINER:pn-glibc-scripts =
> > > "Khem Raj <raj.khem@gmail.com>" +RECIPE_MAINTAINER:pn-glibc-tests
> > > = "Lukasz Majewski <lukma@denx.de>"
> > > RECIPE_MAINTAINER:pn-glibc-testsuite = "Khem Raj
> > > <raj.khem@gmail.com>" RECIPE_MAINTAINER:pn-glide = "Otavio
> > > Salvador <otavio.salvador@ossystems.com.br>"
> > > RECIPE_MAINTAINER:pn-gmp = "Khem Raj <raj.khem@gmail.com>" diff
> > > --git a/meta/conf/distro/include/ptest-packagelists.inc
> > > b/meta/conf/distro/include/ptest-packagelists.inc index
> > > 2e324f8da4..fd52fa72a4 100644 ---
> > > a/meta/conf/distro/include/ptest-packagelists.inc +++
> > > b/meta/conf/distro/include/ptest-packagelists.inc @@ -61,6 +61,7
> > > @@ PTESTS_FAST = "\ slang-ptest \ wayland-ptest \ zlib-ptest \
> > > +    glibc-tests-ptest \  
> > 
> > this will break musl. So lets change this to
> > 
> > PTESTS_FAST:append:libc-glibc = " glibc-tests-ptest"  
> 
> FWIW I tested a tweak in master-next for that...
> 

Shall I prepare v5 with fix for that, or will you keep patches from
master-next (with your fix for this) ?

(I would prefer personally the latter option :-) ).

> 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-11-12  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 15:28 [PATCH v4] glibc: ptest: Add running glibc time related test suite (Y2038) with ptest Lukasz Majewski
2021-11-10 17:12 ` Khem Raj
2021-11-12  8:41   ` [OE-core] " Lukasz Majewski
2021-11-12  8:54     ` Richard Purdie
2021-11-12 15:02       ` Khem Raj
2021-11-11 13:51 ` Khem Raj
2021-11-11 21:28   ` Richard Purdie
2021-11-12  8:48     ` Lukasz Majewski [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=20211112094842.1a636a88@ktm \
    --to=lukma@denx.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=chee.yang.lee@intel.com \
    --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