From: Jeff King <peff@peff•net>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail•com>
Cc: git@vger•kernel.org, Johannes Schindelin <johannes.schindelin@gmx•de>
Subject: Re: [PATCH] ci(dockerized): do show the result of failing tests again
Date: Tue, 18 Nov 2025 04:36:59 -0500 [thread overview]
Message-ID: <20251118093659.GA530545@coredump.intra.peff.net> (raw)
In-Reply-To: <pull.2003.git.1763399064983.gitgitgadget@gmail.com>
On Mon, Nov 17, 2025 at 05:04:24PM +0000, Johannes Schindelin via GitGitGadget wrote:
> The way this signaling works is for the workflow to write into
> special-purpose files whose path is specific to the current workflow
> step and which can be accessed via the `$GITHUB_ENV` environment
> variable, which differs between workflow steps. It is this file that is
> missing write permission for the `builder` user that was introduced in
> above-mentioned commit.
Thanks for fixing this. It bit me recently, but I hadn't had time to
look at it yet.
BTW, I ran into a similar issue (no useful output from a failed test) in
the windows-meson job, but the cause is totally different there:
https://lore.kernel.org/git/20251118093221.GA530337@coredump.intra.peff.net/
-Peff
next prev parent reply other threads:[~2025-11-18 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 17:04 [PATCH] ci(dockerized): do show the result of failing tests again Johannes Schindelin via GitGitGadget
2025-11-17 18:28 ` Junio C Hamano
2025-11-23 2:41 ` Junio C Hamano
2025-11-18 9:36 ` Jeff King [this message]
2025-11-25 6:15 ` Elijah Newren
2025-11-25 14:32 ` Junio C Hamano
2025-11-25 17:40 ` Johannes Schindelin
2025-11-25 19:27 ` Junio C Hamano
2025-11-29 18:31 ` Johannes Schindelin
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=20251118093659.GA530545@coredump.intra.peff.net \
--to=peff@peff$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitgitgadget@gmail$(echo .)com \
--cc=johannes.schindelin@gmx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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