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)
- From: Johannes Schindelin <Johannes.Schindelin@xxxxxx>
- Subject: js/vsts-ci, was Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)
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.