From: Florian Weimer <fweimer@redhat.com>
To: Letu Ren via Libc-help <libc-help@sourceware.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Letu Ren <fantasquex@gmail.com>
Subject: Re: How to skip test when building glibc
Date: Wed, 15 Jun 2022 14:11:33 +0200 [thread overview]
Message-ID: <87o7yup1my.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAEUwDuBcR9ZrVhL3DanWTMMFchrL0nSezOneoDteP+OMKU1wtg@mail.gmail.com> (Letu Ren via Libc-help's message of "Wed, 15 Jun 2022 19:48:16 +0800")
* Letu Ren via Libc-help:
> I encountered 16 test failures. 11 of them are due to timeouts.
> FAIL: nss/tst-nss-files-hosts-getent
> FAIL: nss/tst-nss-files-hosts-multi
> FAIL: string/test-memcpy
> FAIL: string/test-memcpy-large
> FAIL: string/test-mempcpy
> FAIL: stdio-common/tst-vfprintf-width-prec
> FAIL: stdio-common/tst-vfprintf-width-prec-mem
> FAIL: resolv/tst-resolv-res_init-multi
> FAIL: malloc/tst-malloc-too-large-malloc-hugetlb2
> FAIL: nptl/tst-mutex10
> FAIL: locale/tst-localedef-path-norm
Most of them occur regularly on very slow systems (but I haven't seen
nptl/tst-mutex10 and malloc/tst-malloc-too-large-malloc-hugetlb2 in this
context). You could setting TIMEOUT_FACTOR to a large value (like 100)
and retry.
Thanks,
Florian
next prev parent reply other threads:[~2022-06-15 12:11 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 [this message]
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
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=87o7yup1my.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fantasquex@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).