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: Thu, 16 Jun 2022 13:13:11 +0800 [thread overview]
Message-ID: <CAEUwDuB_7cAhnL8XUEgkLxKpKtbN2e_iFoXNUtmuOixAnVAGKw@mail.gmail.com> (raw)
In-Reply-To: <4842386B-AB4B-4B08-BFEC-45B420868B55@linaro.org>
On Thu, Jun 16, 2022 at 4:33 AM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
> I think ideally we should either split the tests that are taking too much time
> or increase the minimum expected timeout (so TIMEOUT_FACTOR is not
> really needed as a default option).
Yes, I totally agree with you. I think I should only increase the
timeout limit to those tests which are necessary. Setting
TIMEOUTFACTOR of all tests to 300 is not a good idea. However I don't
know how to do that. I haven't figured out where the timeout limit is
set after looking through code and doc. Should I report those failures
to glibc bug mailing list, because some of them aren't mentioned in
release notes?
> For the tests that haven’t failed due a TIMEOUT, which are the *.out contents?
stdlib/test-bz22786 is another failure due to a timeout issue, It's
just my carelessness. So we have four failures left. Their *.out
contents are listed below.
# cat math/test-float-j0.out
testing float (without inline functions)
Failure: Test: j0_upward (0x2.67a2a4p+0)
Result:
is: 5.64343701e-08 0x1.e4c47ep-25
should be: 5.64344021e-08 0x1.e4c490p-25
difference: 3.19744232e-14 0x1.200000p-45
ulp : 9.0000
max.ulp : 8.0000
Maximal error of `j0_upward'
is : 9 ulp
accepted: 8 ulp
Test suite completed:
348 test cases plus 344 tests for exception flags and
344 tests for errno executed.
2 errors occurred.
# cat math/test-float32-j0.out
testing _Float32 (without inline functions)
Failure: Test: j0_upward (0x2.67a2a4p+0)
Result:
is: 5.64343701e-08 0x1.e4c47ep-25
should be: 5.64344021e-08 0x1.e4c490p-25
difference: 3.19744232e-14 0x1.200000p-45
ulp : 9.0000
max.ulp : 8.0000
Maximal error of `j0_upward'
is : 9 ulp
accepted: 8 ulp
Test suite completed:
348 test cases plus 344 tests for exception flags and
344 tests for errno executed.
2 errors occurred.
# cat stdlib/tst-strfrom.out
Testing in locale: C
strfromf: got NAN (3), expected -NAN (4)
strfromf32: got NAN (3), expected -NAN (4)
Testing in locale: en_US.ISO-8859-1
strfromf: got NAN (3), expected -NAN (4)
strfromf32: got NAN (3), expected -NAN (4)
Testing in locale: en_US.UTF-8
strfromf: got NAN (3), expected -NAN (4)
strfromf32: got NAN (3), expected -NAN (4)
# cat stdlib/tst-strfrom-locale.out
Testing in locale: de_DE.UTF-8
strfromf: got NAN (3), expected -NAN (4)
strfromf32: got NAN (3), expected -NAN (4)
Testing in locale: tr_TR.ISO-8859-9
strfromf: got NAN (3), expected -NAN (4)
strfromf32: got NAN (3), expected -NAN (4)
Testing in locale: tr_TR.UTF-8
strfromf: got NAN (3), expected -NAN (4)
strfromf32: got NAN (3), expected -NAN (4)
next prev parent reply other threads:[~2022-06-16 5:13 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 [this message]
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
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=CAEUwDuB_7cAhnL8XUEgkLxKpKtbN2e_iFoXNUtmuOixAnVAGKw@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).