From: sundeep.kokkonda@gmail.com
To: "'Libc-help'" <libc-help@sourceware.org>
Subject: RE: glibc test procedure needed
Date: Mon, 11 Jul 2022 14:17:54 +0530 [thread overview]
Message-ID: <000901d89502$eb613840$c223a8c0$@gmail.com> (raw)
In-Reply-To: <004401d89286$20979e70$61c6db50$@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]
> -----Original Message-----
> From: sundeep.kokkonda@gmail.com <sundeep.kokkonda@gmail.com>
> Sent: 08 July 2022 10:20
> To: 'Adhemerval Zanella' <adhemerval.zanella@linaro.org>
> Cc: 'Libc-help' <libc-help@sourceware.org>
> Subject: RE: glibc test procedure needed
>
>
>
> > -----Original Message-----
> > From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> > Sent: 05 July 2022 18:13
> > To: sundeep.kokkonda@gmail.com
> > Cc: Libc-help <libc-help@sourceware.org>
> > Subject: Re: glibc test procedure needed
> >
> >
> >
> > > On 5 Jul 2022, at 03:09, sundeep.kokkonda--- via Libc-alpha <libc-
> > alpha@sourceware.org> wrote:
> > >
> > > Hello,
> > >
> > >
> > >
> > > I need some info on glibc testing.
> > >
> > >
> > >
> > > In the Yocto project we're updating glibc frequently and so we need
> > > to ensure the updated glibc is not introduced any issues, by
> > > performing the testing.
> > >
> > > Can you let me know how can I test glibc? Is there any standardized
> > > test procedure available to do full test/regression test?
> > >
> >
> > The usual ‘make check’ should cover all the required testing, you
> > might need to use ‘run-built-tests=yes’ additional directive if you
> > are cross-compiling to force the make to issues the built tests (for
> > instance on architecture that support multiple ABI, like x86, or to force the use
> of some emulation like qemu-user).
> >
> > We are still fixing up some clunky tests and there are some broken
> > environment (for instance broken syscall filtering) where some tests might
> advertise a failure.
>
> Hello,
>
> I tried with 'Testing with a cross-compiler' method and test is aborted when the
> flag '-Wformat-security' is enabled. When this flag is removed the test is
> executed successfully. Is it a known issue? (The error log make-check.out is
> attached for reference) Also, can anyone share the list of known test failures (if
> any).
>
Hello,
Can I get some info regarding my query.
>
> Thanks,
> Sundeep K.
[-- Attachment #2: make-check.zip --]
[-- Type: application/x-zip-compressed, Size: 391875 bytes --]
next prev parent reply other threads:[~2022-07-11 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 6:09 sundeep.kokkonda
2022-07-05 12:42 ` Adhemerval Zanella
[not found] ` <004401d89286$20979e70$61c6db50$@gmail.com>
2022-07-11 8:47 ` sundeep.kokkonda [this message]
2022-07-11 12:01 ` Adhemerval Zanella
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='000901d89502$eb613840$c223a8c0$@gmail.com' \
--to=sundeep.kokkonda@gmail.com \
--cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).