From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) by sourceware.org (Postfix) with ESMTPS id 97D5D3858016 for ; Wed, 15 Jun 2022 20:33:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 97D5D3858016 Received: by mail-pf1-x42b.google.com with SMTP id e11so12451421pfj.5 for ; Wed, 15 Jun 2022 13:33:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TZyEodLgezfBXLyXEV9jdnVtiZJvJ+nI1m0mHzxNHyg=; b=wLbCG2MAi7iD41Sse1lphdCYHdNhs5G26YKqubIjHiBJb9kACqfmVZIxT1tQBz/5+6 c/La8ix/FFifhMmjLtwxpKGF2HJlzGlAr1QzajfN1MCOCWHl7O1A/t8kFr/Gc6cl06r5 oAD8VPZxklIAsKNVG/XEBOZgg/7qj9gYaoHkXmpisZYI0HpeyPfLGglaMY2fMbCUrloY QHJkEE1gH9uHiBKz5i7bPHUJzTHJaxqHN2uVrM4RE64tc1aenaHU9s47hDmS4ELZCd9p Z/fOs7KLIqkcqPRd9mBzmJsqU8vmhQdhmbq3yWutvNW4pdY3WhIvK3y41TUV9PxuZZaw EGvQ== X-Gm-Message-State: AJIora+iQ1vhXg/R9I3zMGS/zmcRQBNhT0LmVNvF+W0x2ot6syzu3gkR ZJzhUXO3CuKhtL6Jb+2KjbmusA== X-Google-Smtp-Source: AGRyM1tZ6VSWA2iCgK5x7H9sO7IQXSDSOUvACcvoWm4ONyKnHEU2e7mk/AiJojiF6+24gF8cM2UfUA== X-Received: by 2002:a05:6a00:1705:b0:51c:26ae:569c with SMTP id h5-20020a056a00170500b0051c26ae569cmr1263214pfc.28.1655325223602; Wed, 15 Jun 2022 13:33:43 -0700 (PDT) Received: from smtpclient.apple ([192.77.111.2]) by smtp.gmail.com with ESMTPSA id x13-20020a63aa4d000000b003f66a518e48sm10331062pgo.86.2022.06.15.13.33.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Jun 2022 13:33:43 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Subject: Re: How to skip test when building glibc From: Adhemerval Zanella In-Reply-To: Date: Wed, 15 Jun 2022 13:33:42 -0700 Cc: Florian Weimer , Letu Ren via Libc-help Content-Transfer-Encoding: quoted-printable Message-Id: <4842386B-AB4B-4B08-BFEC-45B420868B55@linaro.org> References: <2323859E-CD57-4DB0-88EC-74901E407D35@linaro.org> <87o7yup1my.fsf@oldenburg.str.redhat.com> To: Letu Ren X-Mailer: Apple Mail (2.3696.100.31) X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2022 20:33:46 -0000 > On 15 Jun 2022, at 05:51, Letu Ren wrote: >=20 > On Wed, Jun 15, 2022 at 8:11 PM Florian Weimer = 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. >=20 > Yes, I have figured out the solution to the timeout issue. Do you know > how to deal with other failures? Thanks for replying anyway. >=20 > 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=E2=80=99t failed due a TIMEOUT, which are the = *.out contents?=