git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Jeff King <peff@peff.net>,
	 Anthony Wang <anthonywang513@gmail.com>,
	git@vger.kernel.org
Subject: Re: aw/t9811-modernize, was Re: What's cooking in git.git (Apr 2025, #04; Tue, 15)
Date: Tue, 22 Apr 2025 07:50:30 -0700	[thread overview]
Message-ID: <xmqq8qns5jyh.fsf@gitster.g> (raw)
In-Reply-To: <aActb3dB-r3s69h6@pks.im> (Patrick Steinhardt's message of "Tue, 22 Apr 2025 07:47:27 +0200")

Patrick Steinhardt <ps@pks.im> writes:

> I think the issue is where we put the resulting binaries: they get put
> into "$HOME/path", but the problem is that "$HOME" is different between
> "install-dependencies.sh" and "run-build-and-tests.sh" because the
> latter is executed as unprivileged user.

Yuck.  Thanks for a clealy written explanation and the change.

Will queue.

>
> Something like the below (untested) patch should fix this.
>
> Patrick
>
> [1]: https://gitlab.com/gitlab-org/git/-/jobs/9760840184#L4002
> [2]: https://github.com/git/git/actions/runs/14526556290/job/40759119217#step:8:1814
> [3]: https://github.com/git/git/actions/runs/14526556290/job/40759119217#step:5:2190
>
> -- >8 --
>
> Subject: [PATCH] ci: fix p4d executable not being found on GitHub Actions
>
> Our tests for git-p4(1) depend on the p4d(1) and p4(1) executables to
> exist. As we require specific versions of those binaries which typically
> aren't available on common distributions, we install them manually via
> "ci/install-dependencies.sh".
>
> This script will put the binaries into "$CUSTOM_PATH", which gets
> defined by "ci/lib.sh" -- if not explicitly overridden, its value will
> be set to "$HOME/path". This causes issues though when running our tests
> as unprivileged user, as we do both in GitLab CI and GitHub Actions,
> because "$HOME" will be different when installing dependencies and when
> running the tests. Consequently, the downloaded binaries will not be
> found unless "$CUSTOM_PATH" is overridden to a common location.
>
> We already do this for GitLab CI, where it points to "/custom". Let's do
> the same for GitHub Actions so that Perforce-based tests are executed
> again.
>
> Signed-off-by: Patrick Steinhardt <ps@pks.im>
> ---
>  .github/workflows/main.yml | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> index 83ca8e4182b..412a9a5107b 100644
> --- a/.github/workflows/main.yml
> +++ b/.github/workflows/main.yml
> @@ -408,6 +408,7 @@ jobs:
>        jobname: ${{matrix.vector.jobname}}
>        CC: ${{matrix.vector.cc}}
>        CI_JOB_IMAGE: ${{matrix.vector.image}}
> +      CUSTOM_PATH: /custom
>      runs-on: ubuntu-latest
>      container: ${{matrix.vector.image}}
>      steps:

      reply	other threads:[~2025-04-22 14:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 23:41 What's cooking in git.git (Apr 2025, #04; Tue, 15) Junio C Hamano
2025-04-16 23:18 ` Ramsay Jones
2025-04-18 21:35 ` aw/t9811-modernize, was " Jeff King
2025-04-18 21:38   ` Junio C Hamano
2025-04-18 21:44     ` Junio C Hamano
2025-04-18 21:57       ` Jeff King
2025-04-22  5:47         ` Patrick Steinhardt
2025-04-22 14:50           ` Junio C Hamano [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=xmqq8qns5jyh.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=anthonywang513@gmail.com \
    --cc=git@vger.kernel.org \
    --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 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).