From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 95873 invoked by alias); 28 May 2019 10:15:32 -0000 Mailing-List: contact libabigail-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Id: List-Subscribe: Sender: libabigail-owner@sourceware.org Received: (qmail 95825 invoked by uid 89); 28 May 2019 10:15:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=April, april, officially, arches X-Spam-Status: No, score=-6.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 28 May 2019 10:15:27 +0000 Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 5F94B302BBFE; Tue, 28 May 2019 12:15:19 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 1C463413CC18; Tue, 28 May 2019 12:15:19 +0200 (CEST) Message-ID: Subject: Re: Libabigail release (was: [PATCH v1 00/11] Refactor abg-writer) From: Mark Wielaard To: Matthias Maennich , Dodji Seketeli Cc: libabigail@sourceware.org, kernel-team@android.com Date: Tue, 01 Jan 2019 00:00:00 -0000 In-Reply-To: <20190528081127.GA36623@google.com> References: <20190521043923.203541-1-maennich@google.com> <867eaipt4j.fsf@seketeli.org> <20190523081907.GA99307@google.com> <87pno9m8cz.fsf@seketeli.org> <20190528081127.GA36623@google.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-IsSubscribed: yes X-SW-Source: 2019-q2/txt/msg00125.txt.bz2 Hi, On Tue, 2019-05-28 at 09:11 +0100, Matthias Maennich via libabigail wrote: > Thanks for letting me know. Indeed, the version now being master > contains quite > a lot of new things that I could use in an officially released > version. But I > also agree that we should address the `anonymous struct` > indeterminism first. > Do you know whether this is something newly introduced after the 1.6 > release? > Or has this been seen/reported before? Since it seems to be non-deterministic we don't really know :) I suspect the issue(s) were latent and might just have been exposed because we have more and better tests now. But looking at the buildbot results it seems to have started early April. Somewhere after the following fixes landed: https://sourceware.org/bugzilla/show_bug.cgi?id=3D24410#c2 Since then the buildbot has reported spurious failures. There have been several commits since then to address the issue. And we thought it was fixed. But there is still very occasionally some unexplained failure. I suspect it is some unstable sort or comparison somewhere. But it is subtle and doesn't trigger often. See https://builder.wildebeest.org/buildbot/#/builders?tags=3Dlibabigail for the last 15 changes * 9 arches that the buildbot runs only 3 out of 135 failed. One on x86_64 with FAIL: runtestannotate. One on s390x with FAIL: runtestreaddwarf. And one on ppc64 with FAIL: runtestannotate. They all look somewhat similar. They start with an __anonymous_union__ that has a different type-id-nnn than expected. Cheers, Mark