From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2025, #04; Fri, 14)
Date: Fri, 14 Mar 2025 14:41:30 -0400 [thread overview]
Message-ID: <20250314184130.GA578421@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqv7sbfra0.fsf@gitster.g>
On Fri, Mar 14, 2025 at 10:36:39AM -0700, Junio C Hamano wrote:
> * ps/ci-meson-check-build-docs (2025-03-12) 1 commit
> - ci: perform build and smoke tests for Meson docs
>
> CI update.
>
> Will merge to 'next'.
> source: <20250312-b4-pks-ci-meson-docs-v1-1-5e7cf7ac959a@pks.im>
I didn't dig into it, but I'd imagine this topic is the source of CI
failures on the "documentation" job like this:
2025-03-14T17:50:13.8749066Z + meson setup build-asciidoc -Ddocs=html,man -Ddocs_backend=asciidoc
2025-03-14T17:50:13.8752287Z ci/test-documentation.sh: line 50: meson: command not found
2025-03-14T17:50:13.8769502Z ##[error]Process completed with exit code 127.
that I'm seeing in jch (and looks like you have a similar one in the
latest build of 'seen')
-Peff
next prev parent reply other threads:[~2025-03-14 18:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 17:36 What's cooking in git.git (Mar 2025, #04; Fri, 14) Junio C Hamano
2025-03-14 18:41 ` Jeff King [this message]
2025-03-14 18:42 ` Jeff King
2025-03-15 0:02 ` Junio C Hamano
2025-03-18 15:57 ` [PATCH] install meson for Documentation job Junio C Hamano
2025-03-18 16:19 ` Karthik Nayak
2025-03-18 20:40 ` Junio C Hamano
2025-03-19 9:24 ` Patrick Steinhardt
2025-03-19 16:22 ` Karthik Nayak
2025-03-19 16:33 ` [PATCH] ci/github: add missing 'CI_JOB_IMAGE' env variable Karthik Nayak
2025-03-20 7:10 ` Patrick Steinhardt
2025-03-21 7:51 ` Junio C Hamano
2025-03-20 20:27 ` [PATCH] install meson for Documentation job Junio C Hamano
2025-03-15 0:32 ` en/diff-rename-follow-fix (Was: Re: What's cooking in git.git (Mar 2025, #04; Fri, 14)) Elijah Newren
2025-03-15 1:22 ` en/diff-rename-follow-fix Junio C Hamano
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=20250314184130.GA578421@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).