git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Blume <blume.mike@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] t1410: fix breakage on case-insensitive filesystems
Date: Mon, 10 Nov 2014 01:30:35 -0500	[thread overview]
Message-ID: <20141110063035.GA7677@peff.net> (raw)
In-Reply-To: <xmqqtx28b6z6.fsf@gitster.dls.corp.google.com>

On Sun, Nov 09, 2014 at 09:48:29AM -0800, Junio C Hamano wrote:

> Michael Blume <blume.mike@gmail.com> writes:
> 
> > Works for me, thanks =)
> >
> > I'm curious now, is there an automated build of git running on a mac
> > anywhere? There's a mac mini running jenkins in my office and it's
> > possible I could convince someone to let me set up a git build that'll
> > e-mail me if there's a test failure.
> 
> I am not aware of a Macintosh person who regularly runs tests, but
> if there were, we hopefully will hear from them soonish ;-).

I think there are several people who run the tests on OS X fairly
regularly (I note that another fix for the t1410 problem has already
materialized :) ).

However, I think it is nice when test failures are caught early, before
you have merged topics (to master or elsewhere). That helps isolate the
failures to their particular topics.

I know you "make test" before pushing out the results of any integration
you do. And I recall that for a while (and maybe still?) you even did so
on VMs of a few common platforms. OS X is notoriously irritating to run
in a VM, but would you be interested in a network-accessible install
that you could push to and "make test" on as part of your routine?

If what Michael is offering cannot do that, I am sure I can get GitHub
to set something up.

-Peff

  reply	other threads:[~2014-11-10  6:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08 19:28 Test failure Michael Blume
2014-11-09  1:43 ` Jeff King
2014-11-09  1:59   ` [PATCH] t1410: fix breakage on case-insensitive filesystems Jeff King
2014-11-09 17:34     ` Michael Blume
2014-11-09 17:48       ` Junio C Hamano
2014-11-10  6:30         ` Jeff King [this message]
2014-11-10  6:47           ` Junio C Hamano
2014-11-10  7:04             ` Jeff King
2014-11-09 20:04       ` Torsten Bögershausen
2014-11-09 21:36         ` Michael Blume
2014-11-09 21:42           ` Torsten Bögershausen
2014-11-10  2:46             ` Michael Blume
2014-11-10  2:56     ` Junio C Hamano
2014-11-10  6:09       ` Jeff King
2014-11-12 20:20     ` Johannes Sixt
2014-11-12 21:59       ` Jeff King
2014-11-13  8:50         ` Johannes Sixt
2014-11-13  9:08           ` Jeff King
2014-11-13 16:30             ` Junio C Hamano
2014-11-14 19:11             ` Johannes Sixt
2014-11-14 19:23               ` Jeff King
2014-11-14 20:03               ` Junio C Hamano
2014-11-14 21:04               ` Andreas Schwab
2014-11-15  8:27                 ` Johannes Sixt
2014-11-16 21:06                   ` [PATCH v2] Windows: correct detection of EISDIR in mingw_open() Johannes Sixt
2014-11-09  5:44   ` Test failure Michael Blume

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=20141110063035.GA7677@peff.net \
    --to=peff@peff.net \
    --cc=blume.mike@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).