From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/vsts-ci, was Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)
Date: Wed, 21 Nov 2018 21:11:09 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1811212108180.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqlg5m7qlb.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, 21 Nov 2018, Junio C Hamano wrote:
> * js/vsts-ci (2018-10-16) 13 commits
> . travis: fix skipping tagged releases
> . README: add a build badge (status of the Azure Pipelines build)
> . tests: record more stderr with --write-junit-xml in case of failure
> . tests: include detailed trace logs with --write-junit-xml upon failure
> . git-p4: use `test_atexit` to kill the daemon
> . git-daemon: use `test_atexit` in the tests
> . tests: introduce `test_atexit`
> . ci: add a build definition for Azure DevOps
> . ci/lib.sh: add support for Azure Pipelines
> . tests: optionally write results as JUnit-style .xml
> . test-date: add a subcommand to measure times in shell scripts
> . ci/lib.sh: encapsulate Travis-specific things
> . ci: rename the library of common functions
>
> Prepare to run test suite on Azure DevOps.
>
> Ejected out of 'pu', as doing so seems to help other topics get
> tested at TravisCI.
>
> https://travis-ci.org/git/git/builds/452713184 is a sample of a
> build whose tests on 4 hang (with this series in). Ejecting it
> gave us https://travis-ci.org/git/git/builds/452778963 which still
> shows breakages from other topics not yet in 'next', but at least
> the tests do not stall.
Sorry about that.
FWIW my current plan is to work a bit more on the Windows phase (to make
it faster), and to split out the `test_atexit` patches (because they cause
those hangs). I still think it is the right thing to do, but I lack the
time to take care of it within the next weeks. Instead, I will try to run
even the Windows phase in --verbose-log mode so that the --junit-xml code
can pick up the verbose logs right away (read: no more re-running upon
test failures). Hopefully this won't cause a speed regression.
Ciao,
Dscho
next prev parent reply other threads:[~2018-11-21 20:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 9:00 What's cooking in git.git (Nov 2018, #06; Wed, 21) Junio C Hamano
2018-11-21 10:48 ` Ævar Arnfjörð Bjarmason
2018-11-22 17:53 ` Jeff King
2018-11-22 18:36 ` Ævar Arnfjörð Bjarmason
2018-11-24 12:09 ` Jeff King
2018-11-25 2:02 ` Junio C Hamano
2018-11-26 18:13 ` Jeff King
2018-11-24 2:11 ` Junio C Hamano
2018-11-24 12:06 ` Jeff King
2018-11-21 20:11 ` Johannes Schindelin [this message]
2018-11-21 23:54 ` Stephen P. Smith
2018-11-22 1:06 ` Junio C Hamano
2018-11-22 2:08 ` Stephen P. Smith
2018-11-22 16:05 ` Linus Torvalds
2018-11-22 10:48 ` Ævar Arnfjörð Bjarmason
2018-11-26 21:57 ` Stefan Beller
2018-11-26 23:34 ` Junio C Hamano
2018-12-05 22:04 ` Matthew DeVore
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=nycvar.QRO.7.76.6.1811212108180.41@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--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.
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).