On 2023-08-25 at 08:07 -03, David Bremner <david@tethera.net> wrote:
> Does this failure make any sense to you?
>
>      https://buildd.debian.org/status/fetch.php?pkg=notmuch&arch=ppc64el&ver=0.38%7Erc0-1&stamp=1692959868&raw=0

It doesn't ring any bell. Do you happen to know if this is reproducible
or if we could get a better stack trace?

From what I can tell, there are only three references to g_strdup* in
Notmuch and they seem to be safe. I also couldn't spot any usage of
iconv so it could mean this issue is happening in GLib, like a few
others:
https://git.notmuchmail.org/git?p=notmuch;a=blob;f=test/T810-tsan.suppressions;h=dbd16a94971134c7f675debdfc741f15f2c7abeb;hb=HEAD

So I took a quick look at GLib and their issue tracker but I couldn't
see anything obvious (e.g.: the logging system appears to use iconv when
the console isn't UTF-8 but the Debian build system exports
LC_ALL=C.UTF-8, or sometimes filenames are converted to UTF-8, ...).

> I can just disable tsan tests on ppc64el for Debian, but I wondered if
> there is an underlying bug that only shows up on ppc64el

I can't say if this is unrelated to the architecture but if this test is
too annoying to maintain, feel free to disable it.
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org