From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: js/ci-squelch-doc-warning, was Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)
Date: Mon, 17 Feb 2020 09:08:37 -0800 [thread overview]
Message-ID: <xmqqv9o5kup6.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2002120036570.3718@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 12 Feb 2020 00:39:29 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Mon, 10 Feb 2020, Junio C Hamano wrote:
>
>> * js/ci-squelch-doc-warning (2020-02-10) 1 commit
>> - ci: ignore rubygems warning in the "Documentation" job
>>
>> Squelch unhelpful warning message during documentation build.
>>
>> Will merge to 'next'.
>
> To be clear, this _is_ a warning message, but the CI builds are _failing_
> because of it (the "Documentation" job expects `stderr` to be clean except
> for some known warnings).
>
> As a consequence, all the PR builds at https://github.com/git/git are
> failing (except for PRs targeting `pu` or `next`, but I don't think that
> there are currently any).
>
> So maybe we could fast-track this change all the way into `maint`?
This has happened on Friday at 4e52c1ae ("Merge branch
'js/ci-squelch-doc-warning' into maint", 2020-02-14) and all
integration branches seem to be happy as of last night (I
tentatively dropped a topic or two from 'pu' to make it happen ;-)
Thanks for keeping an eye on the CI results.
next prev parent reply other threads:[~2020-02-17 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 22:29 What's cooking in git.git (Feb 2020, #02; Mon, 10) Junio C Hamano
2020-02-11 23:39 ` js/ci-squelch-doc-warning, was " Johannes Schindelin
2020-02-12 2:19 ` Junio C Hamano
2020-02-12 11:44 ` Johannes Schindelin
2020-02-17 17:08 ` Junio C Hamano [this message]
2020-02-18 14:00 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqv9o5kup6.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).