From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) by sourceware.org (Postfix) with ESMTPS id 924903858292 for ; Tue, 5 Jul 2022 12:43:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 924903858292 Received: by mail-vs1-xe32.google.com with SMTP id i186so11721175vsc.9 for ; Tue, 05 Jul 2022 05:43:00 -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=TFlNdGzRPTBRueQuL/6kmL2TOmzo9q+VnRbxOfhVaAw=; b=zZwrb2qK+p7Fayk+uF+ygeLLx+gslFCKLLNOJmmKWe0xzZOE0ffXQP8iUbI+ziYmqb 3IztHXa0xufl+t3czeip1s1T11TVd4jMnaqaDcChNryneyBZ9tv7qZ5FFOAymyYF2enC X5jsv7OeZdfHPZDjoIXL9O3pcdAC677+WJ89GkmIpHDfZl2ZgpUgzKoDdeO0bEK2bhDi RaPP3aS/HpiS/hsGge4qNDtlP9ZhkuXkFic1K6cWgK9MpIGGwswkUaGhjf2mxYyapXp+ 9lRrakxjfgDO3XMIVFO4rY8mu2pTylxEWQCevvAWvVkQIXHG3vjMUd9DKIEOjZK0ZYBN Baaw== X-Gm-Message-State: AJIora9/jdms91wIj8WrAUy2r1QhU3etj4t2HpmjEnDaG2N4qQU4etQv n4S+kOlFDjpobA4NaxtYBMfuFN8OiAMPZxw4 X-Google-Smtp-Source: AGRyM1tqg1i+nRujN/3ftIhkCGpgWc+uo5AEz66ADCGCWuXzU3chv3WCQ6kdCL/kXOwN/fYS2nUbag== X-Received: by 2002:a67:fe4b:0:b0:356:f7ea:baf1 with SMTP id m11-20020a67fe4b000000b00356f7eabaf1mr1681930vsr.46.1657024979884; Tue, 05 Jul 2022 05:42:59 -0700 (PDT) Received: from smtpclient.apple ([2804:431:c7cb:fef6:fc57:dc88:c1a6:22c5]) by smtp.gmail.com with ESMTPSA id e7-20020a056102034700b00356f1e1e656sm1892591vsa.8.2022.07.05.05.42.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Jul 2022 05:42:59 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Subject: Re: glibc test procedure needed From: Adhemerval Zanella In-Reply-To: <000e01d89035$cf28e5a0$6d7ab0e0$@gmail.com> Date: Tue, 5 Jul 2022 09:42:53 -0300 Cc: Libc-help Content-Transfer-Encoding: quoted-printable Message-Id: References: <000e01d89035$cf28e5a0$6d7ab0e0$@gmail.com> To: sundeep.kokkonda@gmail.com X-Mailer: Apple Mail (2.3696.100.31) X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, 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: Tue, 05 Jul 2022 12:43:02 -0000 > On 5 Jul 2022, at 03:09, sundeep.kokkonda--- via Libc-alpha = wrote: >=20 > Hello, >=20 >=20 >=20 > I need some info on glibc testing. >=20 >=20 >=20 > In the Yocto project we're updating glibc frequently and so we need to > ensure the updated glibc is not introduced any issues, by performing = the > testing. >=20 > Can you let me know how can I test glibc? Is there any standardized = test > procedure available to do full test/regression test? >=20 The usual =E2=80=98make check=E2=80=99 should cover all the required = testing, you might need to use =E2=80=98run-built-tests=3Dyes=E2=80=99 additional directive = if you are cross-compiling to force the make to issues the built tests (for = instance on architecture that support multiple ABI, like x86, or to force the use of some emulation like qemu-user). We are still fixing up some clunky tests and there are some broken=20 environment (for instance broken syscall filtering) where some tests might advertise a failure.