From: Caleb White <cdwhite3@pm.me>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v3 0/8] Allow relative worktree linking to be configured by the user
Date: Thu, 31 Oct 2024 19:52:46 +0000 [thread overview]
Message-ID: <D5A95I1T5FZ6.60QJMN704514@pm.me> (raw)
In-Reply-To: <ZyPYiffYRDK/4LdG@nand.local>
On Thu Oct 31, 2024 at 2:20 PM CDT, Taylor Blau wrote:
> This version of the topic, as well as the previous round, appear to
> break CI:
>
> https://github.com/ttaylorr/git/actions/runs/11602969587
>
> An easy reproduction locally is to run t/t5504-fetch-receive-strict.sh
> when built with 'make SANITIZE=leak' and run with
> 'GIT_TEST_DEFAULT_REF_FORMAT=reftable'.
>
> I'm going to kick this topic out of jch for the time being as it breaks
> CI, but please do send another round once you have fixed the issue. In
> the future, please verify that your series does not break CI before
> sending it to the list. Thanks.
My apologies, I executed
make -j12
cd t
prove -j12 t[0-9]*.sh
(as recommended by t/readme) and everything passed. I did not know I
needed to run the tests with other environment variables set.
Best,
prev parent reply other threads:[~2024-10-31 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 5:05 [PATCH v3 0/8] Allow relative worktree linking to be configured by the user Caleb White
2024-10-31 5:05 ` [PATCH v3 1/8] setup: correctly reinitialize repository version Caleb White
2024-10-31 5:05 ` [PATCH v3 2/8] worktree: add `relativeWorktrees` extension Caleb White
2024-10-31 5:05 ` [PATCH v3 3/8] worktree: refactor infer_backlink return Caleb White
2024-10-31 5:05 ` [PATCH v3 4/8] worktree: add `write_worktree_linking_files()` function Caleb White
2024-10-31 5:05 ` [PATCH v3 5/8] worktree: add relative cli/config options to `add` command Caleb White
2024-10-31 5:06 ` [PATCH v3 6/8] worktree: add relative cli/config options to `move` command Caleb White
2024-10-31 5:06 ` [PATCH v3 7/8] worktree: add relative cli/config options to `repair` command Caleb White
2024-10-31 5:06 ` [PATCH v3 8/8] worktree: refactor `repair_worktree_after_gitdir_move()` Caleb White
2024-10-31 19:20 ` [PATCH v3 0/8] Allow relative worktree linking to be configured by the user Taylor Blau
2024-10-31 19:52 ` Caleb White [this message]
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=D5A95I1T5FZ6.60QJMN704514@pm.me \
--to=cdwhite3@pm.me \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=phillip.wood123@gmail.com \
--cc=sunshine@sunshineco.com \
/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 NNTP newsgroup(s).