All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "René Scharfe" <l.s.r@web.de>,
	"Patrick Steinhardt" <ps@pks.im>
Subject: Re: [PATCH 1/5] test-lib: use individual lsan dir for --stress runs
Date: Mon, 30 Dec 2024 09:08:36 -0800	[thread overview]
Message-ID: <xmqqcyh9yu7f.fsf@gitster.g> (raw)
In-Reply-To: <20241230042401.GA113400@coredump.intra.peff.net> (Jeff King's message of "Sun, 29 Dec 2024 23:24:01 -0500")

Jeff King <peff@peff.net> writes:

> When storing output in test-results/, we usually give each numbered run
> in a --stress set its own output file. But we don't do that for storing
> LSan logs, so something like:
>
>   ./t0003-attributes.sh --stress
>
> will have many scripts simultaneously creating, writing to, and deleting
> the test-results/t0003-attributes.leak directory. This can cause logs
> from one run to be attributed to another, spurious failures when
> creation and deletion race, and so on.
>
> This has always been broken, but nobody noticed because it's rare to do
> a --stress run with LSan (since the point is for the code to run quickly
> many times in order to hit races). But if you're trying to find a race
> in the leak sanitizing code, it makes sense to use these together.

Makes sense.

> We can fix it by using $TEST_RESULTS_BASE, which already incorporates
> the stress job suffix.

Thanks.  Queued.

  parent reply	other threads:[~2024-12-30 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30  4:23 [PATCH 0/5] fixing thread races in linux-leaks CI Jeff King
2024-12-30  4:24 ` [PATCH 1/5] test-lib: use individual lsan dir for --stress runs Jeff King
2024-12-30  4:34   ` Jeff King
2024-12-30 17:08   ` Junio C Hamano [this message]
2024-12-30  4:26 ` [PATCH 2/5] Revert "index-pack: spawn threads atomically" Jeff King
2024-12-30  4:28 ` [PATCH 3/5] thread-utils: introduce optional barrier type Jeff King
2024-12-30  7:03   ` Patrick Steinhardt
2025-01-01 18:28     ` Jeff King
2025-01-03  6:45       ` Patrick Steinhardt
2024-12-30  4:29 ` [PATCH 4/5] index-pack: work around LSan threading race with barrier Jeff King
2024-12-30  4:30 ` [PATCH 5/5] grep: " Jeff King

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=xmqqcyh9yu7f.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=l.s.r@web.de \
    --cc=peff@peff.net \
    --cc=ps@pks.im \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.