git/list[1] front-page[2] threads[3] people[4] search[5] about
 

js/vsts-ci, was Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 21, 2018, 20:11 UTC
Message-ID
<nycvar.QRO.7.76.6.1811212108180.41@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqlg5m7qlb.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, 21 Nov 2018, Junio C Hamano wrote:
Show 25 quoted lines
> * 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

Previous: Jeff KingNext: Stephen P. Smith
Message 10 of 18 in “What's cooking in git.git (Nov 2018, #06; Wed, 21)”
  1. Junio C HamanoNov 21, 2018
  2. Ævar Arnfjörð BjarmasonNov 21, 2018
  3. Jeff KingNov 22, 2018
  4. Ævar Arnfjörð BjarmasonNov 22, 2018
  5. Jeff KingNov 24, 2018
  6. Junio C HamanoNov 25, 2018
  7. Jeff KingNov 26, 2018
  8. Junio C HamanoNov 24, 2018
  9. Jeff KingNov 24, 2018
  10. js/vsts-ci, was Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)Johannes Schindelin, Nov 21, 2018
  11. Stephen P. SmithNov 21, 2018
  12. Junio C HamanoNov 22, 2018
  13. Stephen P. SmithNov 22, 2018
  14. Linus TorvaldsNov 22, 2018
  15. Ævar Arnfjörð BjarmasonNov 22, 2018
  16. Stefan BellerNov 26, 2018
  17. Junio C HamanoNov 26, 2018
  18. Matthew DeVoreDec 5, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.