From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) by sourceware.org (Postfix) with ESMTPS id 8FD6B3861030 for ; Wed, 4 Aug 2021 12:10:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8FD6B3861030 Received: by mail-pj1-x102c.google.com with SMTP id o44-20020a17090a0a2fb0290176ca3e5a2fso3251991pjo.1 for ; Wed, 04 Aug 2021 05:10:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9Xq4cOS9XjPoj2+Lq3DJS72LTruAnDhGhynemRII/4w=; b=LTha4vOJcBJY9C6sLBMeUYIs/dArjMgprlyYqtV5Pl5U8I9HlKZy4SnW7y7n0XjHzz vitodDSvjPQDzJXcCzWr8B9wNkChKV88HjEXt+GfvyNKXF3D2MV3P7uHYl9q4DVqX3uF Sif4XhWm8uoYQ9TnwmzmBBoA9aBCv20TMTBlqKRIhluxa/7+QwmzKutsbwEH4mmkcY9i 7r2Z/0LD1O7kirI9DBUDbt8Vrt3H5lzQfRSXcTCC3D32oAaqe9wiOGs8qlE6kdVMqzZO u7YHYcp387AZycHLDk9RarZAkx0gdo/wsEkVdle9uJsuzcjqvN+LOqqDB7OqRVwUC3H4 +4LA== X-Gm-Message-State: AOAM530nSc8P3QHrM+AB54B66jP2GTM/f/eR/aE0S6aGRu0cU0HuB4U3 k2BrVstAK8pFmp3KuzPGO1nc4ZMAarHYTg== X-Google-Smtp-Source: ABdhPJy1nUKFsGrUlXhj25pXdctGQHROiRqW092b90pSOQquL7P/gudxtjnY3232KynJPI07S/fl5g== X-Received: by 2002:a17:90a:aa05:: with SMTP id k5mr27396757pjq.47.1628079053234; Wed, 04 Aug 2021 05:10:53 -0700 (PDT) Received: from ?IPv6:2804:431:c7ca:76cd:ebc7:4201:855e:55a1? ([2804:431:c7ca:76cd:ebc7:4201:855e:55a1]) by smtp.gmail.com with ESMTPSA id 1sm2395592pjk.54.2021.08.04.05.10.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Aug 2021 05:10:52 -0700 (PDT) Subject: Re: glibc 2.34 failed tests To: Siddhesh Poyarekar Cc: Michael Brunnbauer , libc-help@sourceware.org References: <5f1ce02f-fa75-aa46-bd2f-16f64d210db3@linaro.org> From: Adhemerval Zanella Message-ID: Date: Wed, 4 Aug 2021 09:10:50 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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, 04 Aug 2021 12:10:56 -0000 On 04/08/2021 09:08, Siddhesh Poyarekar wrote: > On Wed, Aug 4, 2021 at 5:33 PM Adhemerval Zanella > wrote: >> On 04/08/2021 09:00, Siddhesh Poyarekar wrote: >>> On Wed, Aug 4, 2021 at 5:26 PM Adhemerval Zanella >>> wrote: >>>>> FAIL: malloc/tst-safe-linking >>>> >>>> Siddhesh has improved it to avoid some false positives, but from from >>>> the commit message it seems that although unlikely it might still be >>>> possible. Could you post the output to see if this is the case? >>> >>> I think Michael said he saw that failure in 2.33 and not on 2.34, >>> which is how it should be with my fix. >> >> But the test was added only on 2.34 (assuming he is testing with the release >> package). Micheal, are you using the source package or some repository revision? > > No, the safe linking test was added in 2.32. Sorry, I meant the other tests (rt/tst-mqueue10 and time/tst-itimer), that's why I think he is testing with 2.34. Also, the message title indicates it as well.