git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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 11, 2020, 23:39 UTC
Message-ID
<nycvar.QRO.7.76.6.2002120036570.3718@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqmu9qxej1.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Mon, 10 Feb 2020, Junio C Hamano wrote:
Show 6 quoted lines
> * 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`?

Thanks, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 6 in “What's cooking in git.git (Feb 2020, #02; Mon, 10)”
  1. Junio C HamanoFeb 10, 2020
  2. js/ci-squelch-doc-warning, was Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)Johannes Schindelin, Feb 11, 2020
  3. Junio C HamanoFeb 12, 2020
  4. Johannes SchindelinFeb 12, 2020
  5. Junio C HamanoFeb 17, 2020
  6. Johannes SchindelinFeb 18, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.