From: Florian Weimer <fweimer@redhat.com>
To: Stefan Liebler <stli@linux.vnet.ibm.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] support: Introduce new subdirectory for test infrastructure
Date: Mon, 12 Dec 2016 22:16:00 -0000 [thread overview]
Message-ID: <be2460fd-ad68-4d96-cb54-244d57cc281d@redhat.com> (raw)
In-Reply-To: <070147db-9e6c-a363-f86a-d86479c1d95f@linux.vnet.ibm.com>
On 12/12/2016 05:38 PM, Stefan Liebler wrote:
>> Can we assume that the test will run to completion with a 300-second
>> timeout (plus TIMEOUTFACTOR scaling)? Then I'll update the test
>> accordingly.
>>
> I don't know how long it lasts on other archs.
> What happens if the testcase timeouts as the testcase expects a SIGALRM?
A timeout is delivered as SIGALARM. :)
So the intent probably is that the test can either exit with 0, or time
out, and both outcomes are fine.
I think this is rather odd. We could express this more clearly with
delayed_exit if this is really our intent here, or we can just keep it
as an xtest with a long timeout, update the comment, and remove the
expected SIGALRM signal because we no longer expect the test to time out
on reasonably current hardware.
Florian
prev parent reply other threads:[~2016-12-12 22:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 20:30 Florian Weimer
2016-11-28 21:51 ` Florian Weimer
2016-11-28 22:58 ` Andreas Schwab
2016-11-29 7:52 ` Florian Weimer
2016-12-02 19:21 ` Carlos O'Donell
2016-12-05 15:57 ` Florian Weimer
2016-12-07 13:20 ` Florian Weimer
2016-12-08 14:29 ` Carlos O'Donell
2016-12-10 15:08 ` Andreas Schwab
2016-12-10 19:17 ` Florian Weimer
2016-12-10 19:39 ` Andreas Schwab
2016-12-12 10:00 ` Florian Weimer
2016-12-12 18:16 ` Andreas Schwab
2016-12-10 15:23 ` [PATCH] Fix testsuite timeout handling Andreas Schwab
2016-12-10 15:36 ` Florian Weimer
2016-11-28 23:11 ` [PATCH] support: Introduce new subdirectory for test infrastructure Joseph Myers
2016-11-29 6:41 ` Florian Weimer
2016-11-30 14:16 ` Carlos O'Donell
2016-12-12 13:12 ` Stefan Liebler
2016-12-12 14:50 ` Florian Weimer
2016-12-12 16:38 ` Stefan Liebler
2016-12-12 22:16 ` Florian Weimer [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=be2460fd-ad68-4d96-cb54-244d57cc281d@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.vnet.ibm.com \
/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).