git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sibi Siddharthan <sibisiv.siddharthan@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2020, #01; Mon, 3)
Date: Wed, 12 Aug 2020 16:11:30 -0400	[thread overview]
Message-ID: <20200812201130.GB1340519@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqlfij63p8.fsf@gitster.c.googlers.com>

On Wed, Aug 12, 2020 at 12:53:39PM -0700, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> > Yeah, I know. My main beef was that because it fails CI, the urgency of
> > doing that fix gets pushed onto people working on their individual
> > topics (in fact there is nothing for you to fix yet because I haven't
> > even sent these topics upstream). I don't know how to solve that without
> > stopping its use in the vsbuild CI job, though.
> 
> What I am not getting is in what way it blocks you (or others who do
> not deeply care about Windows) to leave vsbuild CI job broken.  Do
> you have some automation that is gated by all the CI jobs to pass,
> or do you just dislike failing CI jobs out of principle?

It's two things.

The first is "out of principle". If the vs-build job always fails, then
I'll stop looking at it. So I'd never even see if it fails for a
legitimately interesting reason. And now there's no value in running it
at all.

The second thing is annoyance. I get an email that says "hey, your CI
job failed". And then I think "oh no, I should figure out what it is".
And then I spend 10 minutes investigating only to find out that no, it's
not something I care about.

If the vs-build job always failed I could write it off in less time than
10 minutes. But it's still not nothing, because the email still grabs my
attention, and then I have to manually figure out that it was indeed
vs-build and only vs-build which failed (which is not helped by the mail
from GitHub consisting of 25 lines listing the succeeded jobs). Getting
that once a day isn't world-ending, but it is annoying (and I do get it
once a day because I do my own daily integration run, which is what I
push to CI).

So rather than deal with that, I'd probably add more bits to our
ci/config to allow myself to just disable that job. For now I'm letting
it run, though. I've fixed my two topics, and I'm curious to see if it
comes up again, and if so how long it takes.

-Peff

  reply	other threads:[~2020-08-12 20:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  5:35 What's cooking in git.git (Aug 2020, #01; Mon, 3) Junio C Hamano
2020-08-04 18:50 ` Jeff King
2020-08-04 18:58   ` Junio C Hamano
2020-08-04 19:20     ` Jeff King
2020-08-12 13:35       ` Johannes Schindelin
2020-08-12 14:19         ` Jeff King
2020-08-12 15:56           ` Sibi Siddharthan
2020-08-12 16:06             ` Jeff King
2020-08-12 19:53               ` Junio C Hamano
2020-08-12 20:11                 ` Jeff King [this message]
2020-08-14 12:08               ` Johannes Schindelin
2020-08-14 12:40                 ` Jeff King
2020-08-17  4:41                   ` Johannes Schindelin
2020-08-17 17:19                   ` Junio C Hamano
2020-08-06  3:25 ` Jiang Xin

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=20200812201130.GB1340519@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sibisiv.siddharthan@gmail.com \
    /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).