Re: js/ci-squelch-doc-warning, was Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 17, 2020, 17:08 UTC
Message-ID: <xmqqv9o5kup6.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.2002120036570.3718@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 18 quoted lines

> 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.