From: Taylor Blau <me@ttaylorr.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci: ignore rubygems warning in the "Documentation" job
Date: Sun, 9 Feb 2020 15:03:22 -0800 [thread overview]
Message-ID: <20200209230322.GA4530@syl.local> (raw)
In-Reply-To: <pull.707.git.git.1581287776574.gitgitgadget@gmail.com>
Hi Johannes,
On Sun, Feb 09, 2020 at 10:36:16PM +0000, Johannes Schindelin via GitGitGadget wrote:
> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> A recent update in the Linux VM images used by Azure Pipelines surfaced
> a new problem in the "Documentation" job. Apparently, this warning
> appears 396 times on `stderr` when running `make doc`:
>
> /usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb:10: warning: constant Gem::ConfigMap is deprecated
>
> This problem was already reported to the `rubygems` project via
> https://github.com/rubygems/rubygems/issues/3068.
>
> As there is nothing Git can do about this warning, and as the
> "Documentation" job reports this warning as a failure, let's just
> silence it and move on.
Thanks for explaining, and for taking time to silence errors such as
these that we can't do anything about. Everything as explained makes
good sense to me.
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
> Fix CI/PR failures in the "Documentation" job
>
> It would probably make sense to apply this to maint, too, as it will
> cause CI failures even if there is nothing actionable to be done to
> really fix this on Git's side.
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-707%2Fdscho%2Fworkaround-for-rubygems-using-deprecated-component-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-707/dscho/workaround-for-rubygems-using-deprecated-component-v1
> Pull-Request: https://github.com/git/git/pull/707
>
> ci/test-documentation.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/ci/test-documentation.sh b/ci/test-documentation.sh
> index b3e76ef863..de41888430 100755
> --- a/ci/test-documentation.sh
> +++ b/ci/test-documentation.sh
> @@ -7,6 +7,7 @@
>
> filter_log () {
> sed -e '/^GIT_VERSION = /d' \
> + -e "/constant Gem::ConfigMap is deprecated/d" \
> -e '/^ \* new asciidoc flags$/d' \
> -e '/stripped namespace before processing/d' \
> -e '/Attributed.*IDs for element/d' \
>
> base-commit: d0654dc308b0ba76dd8ed7bbb33c8d8f7aacd783
> --
> gitgitgadget
Thanks,
Taylor
prev parent reply other threads:[~2020-02-09 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 22:36 [PATCH] ci: ignore rubygems warning in the "Documentation" job Johannes Schindelin via GitGitGadget
2020-02-09 23:03 ` Taylor Blau [this message]
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=20200209230322.GA4530@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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).