public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@seketeli.org>
To: Mark Wielaard <mark@klomp.org>
Cc: libabigail@sourceware.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Date: Fri, 20 Mar 2020 23:23:52 +0100	[thread overview]
Message-ID: <864kuism13.fsf@seketeli.org> (raw)
In-Reply-To: <798e09b9cb8940a741afd23a71a89b3d304b0c78.camel@klomp.org> (Mark Wielaard's message of "Thu, 19 Mar 2020 13:25:11 +0100")

Hello Mark,

Mark Wielaard <mark@klomp.org> a écrit:

[...]

>> BUILD FAILED: failed test (failure)
>
> Note that both are big endian. All others (little endian) pass.
>
> The failure is the same:
>
> -found symbol 'foo', an instance of function symbol type of global binding, of versions 'VERSION_2.0', 'VERSION_1.0'
> +could not find symbol 'foo' in file '/home/mjw/bb/wildebeest/libabigail-fedora-s390x/build/tests/data/test-lookup-syms/test1.so'
> FAIL runtestlookupsyms (exit status: 1)
>
> And it happened after:
>
> commit e0950e64279d59e92de5170d805be99f84cdfd8d
> Author: Giuliano Procida <gprocida@google.com>
> Date:   Wed Mar 18 12:12:41 2020 +0000
>
>     dwarf-reader: Use all bits of Bloom filter words.
>
> Staring at the code it might certainly be that some words are swapped
> in the big-endian case, but I am not seeing it (nor do I really
> understand the whole algorithm, so...)
>

Thanks for this analysis.  The patch
https://sourceware.org/git/?p=libabigail.git;a=commit;h=b1b0586dc208726bd5de5728caf1ead119413fce
should hopefully address that issue.

I'll be monitoring the builders to see if they are happy now.

Cheers,

-- 
		Dodji

  reply	other threads:[~2020-03-20 22:23 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 10:55 buildbot
2020-03-19 12:25 ` Mark Wielaard
2020-03-20 22:23   ` Dodji Seketeli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-17 13:19 buildbot
2021-12-21 19:18 buildbot
2021-12-14 15:55 buildbot
2021-12-15 13:01 ` Mark Wielaard
2021-11-29  8:05 buildbot
2021-11-29 11:23 ` Mark Wielaard
2021-10-27 11:11 buildbot
2021-10-27 11:14 ` Mark Wielaard
2021-10-27 12:04   ` Dodji Seketeli
2021-10-18 10:58 buildbot
2021-09-23 12:12 buildbot
2021-09-23 12:19 ` Mark Wielaard
2021-08-11 17:08 buildbot
2021-07-16 10:11 buildbot
2021-07-16 10:33 ` Mark Wielaard
2021-04-12 15:48 buildbot
2021-03-18 16:05 buildbot
2021-03-19 23:03 ` Mark Wielaard
2020-12-02 15:32 buildbot
2020-11-27 16:59 buildbot
2020-11-25 12:52 buildbot
2020-11-25  8:51 buildbot
2020-11-12 10:50 buildbot
2020-11-02 17:21 buildbot
2020-10-27  9:47 buildbot
2020-10-27 11:30 ` Mark Wielaard
2020-10-27 13:12   ` Mark Wielaard
2020-10-28  9:30     ` Dodji Seketeli
2020-10-28 10:12       ` Mark Wielaard
2020-10-14 10:31 buildbot
2020-10-09  9:35 buildbot
2020-07-30 15:29 buildbot
2020-07-30 15:38 ` Mark Wielaard
2020-07-28 14:40 buildbot
2020-07-28 14:41 ` Mark Wielaard
2020-05-04  9:36 buildbot
2020-04-23 13:09 buildbot
2020-04-23 13:32 ` Mark Wielaard
2020-03-26 15:47 buildbot
2020-03-12 13:41 buildbot
2020-01-01  0:00 buildbot
2020-01-01  0:00 buildbot
2020-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Matthias Maennich via libabigail
2019-01-01  0:00   ` Mark Wielaard
2019-01-01  0:00     ` Matthias Maennich via libabigail
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00   ` Dodji Seketeli
2019-01-01  0:00     ` Mark Wielaard
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00   ` Dodji Seketeli
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00   ` Dodji Seketeli
2019-01-01  0:00     ` Mark Wielaard
2019-01-01  0:00       ` Dodji Seketeli
2019-01-01  0:00     ` Mark Wielaard
2019-01-01  0:00       ` Dodji Seketeli
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2018-01-01  0:00 buildbot
2018-01-01  0:00 ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864kuism13.fsf@seketeli.org \
    --to=dodji@seketeli.org \
    --cc=libabigail@sourceware.org \
    --cc=mark@klomp.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).