From: Letu Ren <fantasquex@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Letu Ren via Libc-help <libc-help@sourceware.org>
Subject: Re: How to skip test when building glibc
Date: Wed, 17 Aug 2022 16:19:25 +0800 [thread overview]
Message-ID: <CAEUwDuDDpkLOQtF69OdGHbEqwzjtnpAm2qQ88ihyW0dCVSDCJg@mail.gmail.com> (raw)
In-Reply-To: <F76503BC-127B-448C-AD59-DB00C8A8C429@linaro.org>
Hi,
First, I'm really sorry for my late reply.
> The default configuration for all testcases is to create a helper parent
> process to handle timeout and spurious failures (such as segfault). You
> can disable it by using the —direct command line with testrun.sh (which
> runs the test using the built glibc loader and libraries):
>
> builddir$ time ./testrun testcase —direct
>
> Some tests might require additional environment variables or arguments,
> easiest way to check is to get them is to copy from make check log.
Thanks a lot. Now I know how to calculate time consumed by each failing test.
> So you are indeed testing against the real hardware. Could you open a
> bug report [1] with the output of ‘make regen-ulps’ ? I think we will
> need to update the minimum required ULPs.
>
> It can be also a regression on compiler that is generating larger error
> bounds, since the current ULP baseline seems also to be generated on
> read hardware.
As glibc 2.36 was released several days ago, I rerun testsuite with
glibc 2.36. This issue is fixed.
> Could you also open another bug report with the output of the testcases?
OK, I have filed several bug reports to bugzilla.
https://sourceware.org/bugzilla/show_bug.cgi?id=29501
https://sourceware.org/bugzilla/show_bug.cgi?id=29500
https://sourceware.org/bugzilla/show_bug.cgi?id=29499
Thank you very much for your kind help.
Letu Ren
prev parent reply other threads:[~2022-08-17 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 6:49 Letu Ren
2022-06-14 23:15 ` Adhemerval Zanella
2022-06-15 11:48 ` Letu Ren
2022-06-15 12:11 ` Florian Weimer
2022-06-15 12:51 ` Letu Ren
2022-06-15 20:33 ` Adhemerval Zanella
2022-06-16 5:13 ` Letu Ren
2022-06-16 17:43 ` Adhemerval Zanella
2022-06-17 8:12 ` Letu Ren
2022-06-21 12:21 ` Adhemerval Zanella
2022-08-17 8:19 ` Letu Ren [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=CAEUwDuDDpkLOQtF69OdGHbEqwzjtnpAm2qQ88ihyW0dCVSDCJg@mail.gmail.com \
--to=fantasquex@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.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).