From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Letu Ren <fantasquex@gmail.com>
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, 15 Jun 2022 13:33:42 -0700 [thread overview]
Message-ID: <4842386B-AB4B-4B08-BFEC-45B420868B55@linaro.org> (raw)
In-Reply-To: <CAEUwDuD18uuL_rUt4umVpLJjgQ3LsYMTPpO0Gzqtqzsz7GqW4w@mail.gmail.com>
> On 15 Jun 2022, at 05:51, Letu Ren <fantasquex@gmail.com> wrote:
>
> On Wed, Jun 15, 2022 at 8:11 PM Florian Weimer <fweimer@redhat.com> wrote:
>> 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.
>
> Yes, I have figured out the solution to the timeout issue. Do you know
> how to deal with other failures? Thanks for replying anyway.
>
> Letu Ren
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).
For the tests that haven’t failed due a TIMEOUT, which are the *.out contents?
next prev parent reply other threads:[~2022-06-15 20:33 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 [this message]
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=4842386B-AB4B-4B08-BFEC-45B420868B55@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fantasquex@gmail.com \
--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).