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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 18, 2020, 14:00 UTC
Message-ID: <nycvar.QRO.7.76.6.2002181500210.46@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqqv9o5kup6.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Mon, 17 Feb 2020, Junio C Hamano wrote:

Show 25 quoted lines

> 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 ;-)

I noticed ;-) Thanks for merging all of this down to `maint`.

Ciao, Dscho

> Thanks for keeping an eye on the CI results.
>
>