From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: David Bremner <david@tethera.net>
Cc: Kevin Boulain <kevin@boula.in>, notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] test: showcase thread-unsafe s-expression query parser
Date: Sun, 23 Jul 2023 15:23:26 +0200 [thread overview]
Message-ID: <CAA19uiQC8DoLBGUb-dhV1uq=we=ZV8+F2t=muJsrHpkZBjoCfg@mail.gmail.com> (raw)
In-Reply-To: <87ilabg4u1.fsf@tethera.net>
Am Sa., 22. Juli 2023 um 20:48 Uhr schrieb David Bremner <david@tethera.net>:
>
> Kevin Boulain <kevin@boula.in> writes:
>
> > The test fails quite reliably for me:
> > T810-tsan: Testing run code with TSan enabled against the library
> > PASS create
> > PASS query
> > FAIL sexp query
>
> I can't get this test to fail at all. I'm not sure what to conclude from
> that. This is on a 20 core system running linux.
This might be completely unrelated, but I recall a strange problem I
had with asan (not tsan): We build without asan, but if asan is
present for whatever reason then the tests are run nonetheless. So we
had to disable asan tests explicitly. Is your sexp compiled
accordingly?
Michael
next prev parent reply other threads:[~2023-07-23 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 20:31 [PATCH 1/2] test: showcase thread-unsafe s-expression query parser Kevin Boulain
2023-04-03 20:31 ` [PATCH 2/2] lib: thread-safe " Kevin Boulain
2023-07-22 19:06 ` David Bremner
2023-08-27 12:31 ` [PATCH v2 1/2] test: showcase thread-unsafe " Kevin Boulain
2023-09-19 10:30 ` David Bremner
2023-08-27 12:31 ` [PATCH v2 2/2] lib: thread-safe " Kevin Boulain
2023-08-27 12:33 ` [PATCH " Kevin Boulain
2023-07-22 18:48 ` [PATCH 1/2] test: showcase thread-unsafe " David Bremner
2023-07-23 13:23 ` Michael J Gruber [this message]
2023-07-23 14:03 ` David Bremner
2023-08-06 10:05 ` Kevin Boulain
2023-08-06 12:01 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA19uiQC8DoLBGUb-dhV1uq=we=ZV8+F2t=muJsrHpkZBjoCfg@mail.gmail.com' \
--to=michaeljgruber+grubix+git@gmail.com \
--cc=david@tethera.net \
--cc=kevin@boula.in \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).