This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |