From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 1/2] ci(coverity): fix building on Windows
Date: Wed, 11 Jun 2025 07:24:47 -0700 [thread overview]
Message-ID: <xmqqtt4mjqz4.fsf@gitster.g> (raw)
In-Reply-To: <c65120f25704e9725c317a62b9a1231bd19f3e25.1749650552.git.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Wed, 11 Jun 2025 14:02:31 +0000")
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> ...
> In the meantime, the current Coverity documentation describes a very
> different way to install the analysis tool, recommending to add the
> `bin/` directory to the _end_ of `PATH` (when originally, IIRC, it was
> recommended to add it to the _beginning_ of the `PATH`).
> ..., and finding the "wrong" ones first on the
> `PATH` misleads that logic.
>
> Let's fix this problem by following Coverity's current recommendation
> and append the `bin/` directory in which `cov-int` can be found to the
> _end_ of `PATH`.
Wow, that is a very well described change.
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
> .github/workflows/coverity.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.github/workflows/coverity.yml b/.github/workflows/coverity.yml
> index 124301dbbe2f..a5d99e59d4eb 100644
> --- a/.github/workflows/coverity.yml
> +++ b/.github/workflows/coverity.yml
> @@ -147,7 +147,7 @@ jobs:
> key: cov-build-${{ env.COVERITY_LANGUAGE }}-${{ env.COVERITY_PLATFORM }}-${{ steps.lookup.outputs.hash }}
> - name: build with cov-build
> run: |
> - export PATH="$RUNNER_TEMP/cov-analysis/bin:$PATH" &&
> + export PATH="$PATH:$(cygpath -au "$RUNNER_TEMP")/cov-analysis/bin" &&
Additionally two things are lacking explanation in the proposed log
message, though, or an uninitiated will still be left scratching his
head:
- Why didn't the original need "cygpath -au"?
- Even though many steps in this job deals with different
env.COVERITY_PLATFORM, this part does not seem to be conditional.
Why is $(cygpath -au ...) safe outside Windows environment?
Other than that, nicely done and very nicely explained.
> cov-configure --gcc &&
> cov-build --dir cov-int make
> - name: package the build
next prev parent reply other threads:[~2025-06-11 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 14:02 [PATCH 0/2] Fix Coverity builds on Windows Johannes Schindelin via GitGitGadget
2025-06-11 14:02 ` [PATCH 1/2] ci(coverity): fix building " Johannes Schindelin via GitGitGadget
2025-06-11 14:24 ` Junio C Hamano [this message]
2025-06-11 15:53 ` Johannes Schindelin
2025-06-11 17:27 ` Junio C Hamano
2025-06-11 14:02 ` [PATCH 2/2] ci(coverity): output the build log upon error Johannes Schindelin via GitGitGadget
2025-06-11 14:25 ` Junio C Hamano
2025-06-11 15:54 ` [PATCH v2 0/2] Fix Coverity builds on Windows Johannes Schindelin via GitGitGadget
2025-06-11 15:54 ` [PATCH v2 1/2] ci(coverity): fix building " Johannes Schindelin via GitGitGadget
2025-06-11 15:54 ` [PATCH v2 2/2] ci(coverity): output the build log upon error Johannes Schindelin via GitGitGadget
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=xmqqtt4mjqz4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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