From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
Daniel Stenberg <daniel@haxx.se>,
Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>,
Samuel Lijin <sxlijin@gmail.com>
Subject: Re: [PATCH v2] travis-ci: build and test Git on Windows
Date: Thu, 30 Mar 2017 01:26:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1703300119310.4068@virtualbox> (raw)
In-Reply-To: <CAHGBnuPdve_5Xrmde6cjbXBjSWfZLrT5eT90hayG0jfbBTkq6Q@mail.gmail.com>
Hi,
On Fri, 24 Mar 2017, Sebastian Schuberth wrote:
> On Fri, Mar 24, 2017 at 1:35 PM, Lars Schneider
> <larsxschneider@gmail.com> wrote:
>
> >> 1. use appveyor.com, as that is a Travis-like service for Windows. We do our
> >> windows-builds in the curl project using that.
> >
> > The Git for Windows build and tests are *really* resources intensive and they
> > take a lot of setup time. AFAIK we would run into timeouts with AppVeyor.
> > Maybe Sebastian or Dscho know details?
>
> At lot of setup time, in terms of installing the Git for Windows SDK,
> could probably be saved by only installing the required packages on
> top of MSYS2 that's already installed in AppVeyor nodes [1].
>
> [1] https://www.appveyor.com/docs/build-environment/#mingw-msys-cygwin
And that is indeed what Git for Windows' Git fork has configured. Sadly,
the job timed out too often for me, even if I disabled the tests.
As of recent, things turned more green, with the build taking only about 3
minutes. Of course, re-enabling the tests would let us run smack into the
20 minutes time out, *and* we still would have to disable the tests that
fail because MSYS2's maintainer ignored the PRs trying to integrate Git
for Windows' patches to the MSYS2 runtime.
Example for a green job:
https://ci.appveyor.com/project/dscho/git/build/1.0.676
Ciao,
Johannes
next prev parent reply other threads:[~2017-03-29 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 11:37 [PATCH v2] travis-ci: build and test Git on Windows Lars Schneider
2017-03-24 11:48 ` Daniel Stenberg
2017-03-24 12:35 ` Lars Schneider
2017-03-24 12:42 ` Daniel Stenberg
2017-03-24 12:43 ` Sebastian Schuberth
2017-03-29 23:26 ` Johannes Schindelin [this message]
2017-03-24 14:59 ` Jeff King
2017-03-24 16:58 ` Junio C Hamano
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=alpine.DEB.2.20.1703300119310.4068@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=daniel@haxx.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
--cc=sschuberth@gmail.com \
--cc=sxlijin@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).