Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jan 29, 2019, 14:21 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1901291518550.41@tvgsbejvaqbjf.bet>
- In-Reply-To
- <xmqq4l9s9zee.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Mon, 28 Jan 2019, Junio C Hamano wrote:
Show 26 quoted lines
> * js/vsts-ci (2019-01-28) 21 commits > - ci: parallelize testing on Windows > - ci: speed up Windows phase > - tests: optionally skip bin-wrappers/ > - t0061: fix with --with-dashes and RUNTIME_PREFIX > - tests: add t/helper/ to the PATH with --with-dashes > - mingw: try to work around issues with the test cleanup > - tests: include detailed trace logs with --write-junit-xml upon failure > - tests: avoid calling Perl just to determine file sizes > - README: add a build badge (status of the Azure Pipelines build) > - mingw: be more generous when wrapping up the setitimer() emulation > - ci: use git-sdk-64-minimal build artifact > - ci: add a Windows job to the Azure Pipelines definition > - 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: use a junction on Windows instead of a symlink > - ci: inherit --jobs via MAKEFLAGS in run-build-and-tests > - ci/lib.sh: encapsulate Travis-specific things > - ci: rename the library of common functions > - travis: fix skipping tagged releases > > Prepare to run test suite on Azure Pipeline. > > Will merge to 'next'.
To make it easier for you (or at least I *hope* that that makes it easier for you), I just submitted v6 (<pull.31.v6.git.gitgitgadget@gmail.com>), which includes a fix for a sparse warning reported by Ramsay, and a touched-up commit message to explain why RUNTIME_PREFIX cannot be made to work in test helpers, as you suggested.
Please pick up v6 instead of v5 before merging to `next`, it really only has a very small range-diff relative to v5.
Thanks, Dscho