Message ID | b063169a-ac91-8b6d-f052-b7b75e4534ce@redhat.com |
---|---|
State | Committed |
Headers |
Received: (qmail 76079 invoked by alias); 18 May 2017 18:59:41 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <libc-alpha.sourceware.org> List-Unsubscribe: <mailto:libc-alpha-unsubscribe-##L=##H@sourceware.org> List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org> List-Archive: <http://sourceware.org/ml/libc-alpha/> List-Post: <mailto:libc-alpha@sourceware.org> List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs> Sender: libc-alpha-owner@sourceware.org Delivered-To: mailing list libc-alpha@sourceware.org Received: (qmail 76065 invoked by uid 89); 18 May 2017 18:59:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-26.4 required=5.0 tests=BAYES_00, GIT_PATCH_0, GIT_PATCH_1, GIT_PATCH_2, GIT_PATCH_3, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=ham version=3.3.2 spammy=Hx-languages-length:1193, HX-Received:10.55.66.80 X-HELO: mail-qk0-f180.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=3uiB8kc7TczxB5oOjOPETjTjLt7gclPLrXCSKeGBJic=; b=BZmE2Z1MOhZ8jSUT3mjDsw2B0VWXczsBhu7WUwI0ZCOwqd+w24GAuPvGaTxRnFDgfv 25SDAdFG435W0kd1isMUjoSJ6CYpTXvGqzp4bLIUBt8k1DDsYMVr+nR3htt4XY+vL3Ik HrHvygd1AcXJEDxqFBdrLgM7smXJwbVSXuXGvVti5Xs0xI4KSp+VZbql7rxZsX7eZTGg /+K3EZ9mrLBK6FBVy8XT8CI7Hj72At70dwd6i9VtjAhjpmqiVcTKJOd9KrCEbl39c3+U Dj4zuc1cYL1/tz5fwr71zxNIlZy0t6TVi3nNZPwAgy8YvCyTs9C82bhZGjmWf/IoNwQI vOFg== X-Gm-Message-State: AODbwcB7RMls6+Bqh76bA8MYVrvxAAeOneySBy3juzqmcLAcI+lCZSnK 8ujZyI8OQCsd7wyNABjcwg== X-Received: by 10.55.66.80 with SMTP id p77mr4958116qka.225.1495133981003; Thu, 18 May 2017 11:59:41 -0700 (PDT) To: GNU C Library <libc-alpha@sourceware.org> From: Carlos O'Donell <carlos@redhat.com> Subject: [PATCH] nptl/tst-robust-fork: Increase timeout to 30 seconds. Message-ID: <b063169a-ac91-8b6d-f052-b7b75e4534ce@redhat.com> Date: Thu, 18 May 2017 14:59:38 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit |
Commit Message
Carlos O'Donell
May 18, 2017, 6:59 p.m. UTC
The default test timeout is 20 seconds. On certain x86_64 hardware I can see tst-robust-fork test take 22 seconds on average. This results in spurious failures. I suggest we increase the timeout to 25 seconds and add a note about this. If nobody objects I'll check this in at some point next week when I get a free minute. I don't know if it's particularly useful to list the kernel version or hardware under which the slow timing came from i.e. linux 4.10 on an older i5-4690K. 2017-05-18 Carlos O'Donell <carlos@redhat.com> * nptl/tst-robust-fork.c (TIMEOUT): Define. ---
Comments
On Friday 19 May 2017 12:29 AM, Carlos O'Donell wrote: > The default test timeout is 20 seconds. > > On certain x86_64 hardware I can see tst-robust-fork test take 22 seconds on average. > > This results in spurious failures. > > I suggest we increase the timeout to 25 seconds and add a note about this. > > If nobody objects I'll check this in at some point next week when I get a > free minute. > > I don't know if it's particularly useful to list the kernel version or > hardware under which the slow timing came from i.e. linux 4.10 on an older > i5-4690K. LGTM. Siddhesh
Carlos O'Donell <carlos@redhat.com> writes: > The default test timeout is 20 seconds. > > On certain x86_64 hardware I can see tst-robust-fork test take 22 seconds on average. > > This results in spurious failures. > > I suggest we increase the timeout to 25 seconds and add a note about this. > > If nobody objects I'll check this in at some point next week when I get a > free minute. > > I don't know if it's particularly useful to list the kernel version or > hardware under which the slow timing came from i.e. linux 4.10 on an older > i5-4690K. > > 2017-05-18 Carlos O'Donell <carlos@redhat.com> > > * nptl/tst-robust-fork.c (TIMEOUT): Define. I agree with this change. I have already proposed another patch increasing it to 35s [1]. IMO, 25 is too close to the time we both measured. By the way, it isn't restricted to x86_64. I've seen this on powerpc as well. [1] https://patchwork.sourceware.org/patch/19174/
On 18/05/2017 15:59, Carlos O'Donell wrote: > The default test timeout is 20 seconds. > > On certain x86_64 hardware I can see tst-robust-fork test take 22 seconds on average. > > This results in spurious failures. > > I suggest we increase the timeout to 25 seconds and add a note about this. > > If nobody objects I'll check this in at some point next week when I get a > free minute. > > I don't know if it's particularly useful to list the kernel version or > hardware under which the slow timing came from i.e. linux 4.10 on an older > i5-4690K. Which are the constraint that increase the time required for such test (cpu count, latency, memory latency, kernel version, etc.)? > > 2017-05-18 Carlos O'Donell <carlos@redhat.com> > > * nptl/tst-robust-fork.c (TIMEOUT): Define. > > diff --git a/nptl/tst-robust-fork.c b/nptl/tst-robust-fork.c > index 4a12ff0..d2c8a5a 100644 > --- a/nptl/tst-robust-fork.c > +++ b/nptl/tst-robust-fork.c > @@ -25,6 +25,12 @@ > #include <support/xunistd.h> > #include <sys/mman.h> > > +/* This test can take as long as 22 seconds on some x86_64 hardware, > + so increase the timeout to 25 seconds to allow it to pass. More > + than half of the time is spent in page_fault() in the kernel and > + do_lookup_x() in ld.so. */ > +#define TIMEOUT 25 > + > /* Data shared between processes. */ > struct shared > { > --- >
diff --git a/nptl/tst-robust-fork.c b/nptl/tst-robust-fork.c index 4a12ff0..d2c8a5a 100644 --- a/nptl/tst-robust-fork.c +++ b/nptl/tst-robust-fork.c @@ -25,6 +25,12 @@ #include <support/xunistd.h> #include <sys/mman.h> +/* This test can take as long as 22 seconds on some x86_64 hardware, + so increase the timeout to 25 seconds to allow it to pass. More + than half of the time is spent in page_fault() in the kernel and + do_lookup_x() in ld.so. */ +#define TIMEOUT 25 + /* Data shared between processes. */ struct shared {