From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) by sourceware.org (Postfix) with ESMTPS id 204E63858D1E for ; Wed, 17 Aug 2022 08:19:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 204E63858D1E Received: by mail-pj1-x102f.google.com with SMTP id s5-20020a17090a13c500b001f4da9ffe5fso1143519pjf.5 for ; Wed, 17 Aug 2022 01:19:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc; bh=5mWLF5SPDrf993Ffab6ZU8hkRUmdrpBV8I9tjOpGgZI=; b=dQBDunCW1p2qG+yxHrx0yWr4HJj7a/GMIC6c4UtvcLB0V9obOvTbjiuy16tvmDJQO/ JkdLUS5XYharP/MKwPv2RGax1rOEgFbBcPYrTmAovNI4n0F+39JMwzS+PlUQedQj5Cxk 0cvRJ4a3Eb/ZPcMFOmEZxNwo+FeUKdFb2b9CHthYr88XHtFzlGCcd1SxF5ZkJu35O4Ig qIBLN7l7PUjs0ZmT4ZpHWJJt8LcjGU7LXt0GAEYDxFaY+uh56bdc2z0OkktDF64asPgt erk+vemqO9XEWo5rvcgIxlR1EIFCzzK657RHfAgFzPoudCn72NMRYXv2hGqfKaONzmCH m+jA== X-Gm-Message-State: ACgBeo3h76yJVlSoZ4teU6K3lHQKH0Gys3hJoIY0d8ZqCk4k4qoZAt5y rBIcluqj4rI+RIJ4BCbHRq/TnuDD+0TpJ9Egof8= X-Google-Smtp-Source: AA6agR76ZhaUDDk1ChRdfMEQzwUWIocdunYwK1PZ4us7sG0+6JH+6POZxJgI4pAWKbms96WFS1LFW7q/Fqg5lGDxVsw= X-Received: by 2002:a17:902:7293:b0:16f:17c3:e809 with SMTP id d19-20020a170902729300b0016f17c3e809mr25670358pll.158.1660724378164; Wed, 17 Aug 2022 01:19:38 -0700 (PDT) MIME-Version: 1.0 References: <2323859E-CD57-4DB0-88EC-74901E407D35@linaro.org> <87o7yup1my.fsf@oldenburg.str.redhat.com> <4842386B-AB4B-4B08-BFEC-45B420868B55@linaro.org> <6FE8D53C-2116-49FD-B9EF-1328AEBEF16A@linaro.org> In-Reply-To: From: Letu Ren Date: Wed, 17 Aug 2022 16:19:25 +0800 Message-ID: Subject: Re: How to skip test when building glibc To: Adhemerval Zanella Cc: Florian Weimer , Letu Ren via Libc-help Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham 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, 17 Aug 2022 08:19:40 -0000 Hi, First, I'm really sorry for my late reply. > The default configuration for all testcases is to create a helper parent > process to handle timeout and spurious failures (such as segfault). You > can disable it by using the =E2=80=94direct command line with testrun.sh = (which > runs the test using the built glibc loader and libraries): > > builddir$ time ./testrun testcase =E2=80=94direct > > Some tests might require additional environment variables or arguments, > easiest way to check is to get them is to copy from make check log. Thanks a lot. Now I know how to calculate time consumed by each failing tes= t. > So you are indeed testing against the real hardware. Could you open a > bug report [1] with the output of =E2=80=98make regen-ulps=E2=80=99 ? I t= hink we will > need to update the minimum required ULPs. > > It can be also a regression on compiler that is generating larger error > bounds, since the current ULP baseline seems also to be generated on > read hardware. As glibc 2.36 was released several days ago, I rerun testsuite with glibc 2.36. This issue is fixed. > Could you also open another bug report with the output of the testcases? OK, I have filed several bug reports to bugzilla. https://sourceware.org/bugzilla/show_bug.cgi?id=3D29501 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29500 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29499 Thank you very much for your kind help. Letu Ren