From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Arjun Shankar <arjun.is@lostca.se>,
libc-alpha@sourceware.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH] Fix integer overflows in internal memalign and malloc functions [BZ #22343]
Date: Fri, 19 Jan 2018 08:32:00 -0000 [thread overview]
Message-ID: <780150f2-3711-40bf-9456-d934ca5a8e03@redhat.com> (raw)
In-Reply-To: <6f1f5c46-955b-1cec-e664-faef7fdd74e3@redhat.com>
On 01/18/2018 12:04 AM, Florian Weimer wrote:
> On 01/17/2018 10:45 PM, Carlos O'Donell wrote:
>> You are absolutely right, I thought the default was 2 seconds, but
>> that's just my age showing... the old test-skeleton.c had a 2 second
>> timeout. That has changed to 20 seconds with the new support framework.
>
> The original change of the timeout was made in test-skeleton.c and
> predates support/. I had to check because I did not remember
> changing it.
You are right, sorry, I see it was changed in a28605b22946c708f0a5c4f06307e1a17650ced8
on January 19th 2016 (2 years to the day). Not really "old" enough for it to
have seeped into our collective expectations :-)
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-01-19 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 20:26 Arjun Shankar
2018-01-17 20:52 ` Florian Weimer
2018-01-17 21:47 ` Carlos O'Donell
2018-01-18 8:04 ` Florian Weimer
2018-01-19 8:32 ` Carlos O'Donell [this message]
2018-01-17 22:01 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2018-01-04 17:02 Arjun Shankar
2018-01-04 17:20 ` Zack Weinberg
2018-01-04 20:32 ` Paul Eggert
2018-01-04 23:07 ` Carlos O'Donell
2018-01-16 16:27 ` Arjun Shankar
2018-01-16 21:00 ` Carlos O'Donell
2018-01-17 6:27 ` Paul Eggert
2018-01-17 14:59 ` Carlos O'Donell
2018-01-16 22:31 ` Carlos O'Donell
2018-01-16 22:56 ` Carlos O'Donell
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=780150f2-3711-40bf-9456-d934ca5a8e03@redhat.com \
--to=carlos@redhat.com \
--cc=arjun.is@lostca.se \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).