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

Re: Git Test Coverage Report (Saturday, Oct 27)

From
Derrick Stolee <stolee@gmail.com>
Date
Oct 27, 2018, 19:47 UTC
Message-ID
<649cac55-7fb0-d23b-eaf6-6f1dab30a0da@gmail.com>
In-Reply-To
<xmqqsh0ra3yx.fsf@gitster-ct.c.googlers.com>
On 10/27/2018 9:55 AM, Junio C Hamano wrote:
Show 7 quoted lines
> Derrick Stolee <stolee@gmail.com> writes:
>
>
>> Uncovered in mater not in master@{1}
>> ------------------------------------
> Does this typo indicate that some part of the process to produce and
> send out this report involve manual editing?

I kick off four builds with on Azure Pipelines [1], wait for the builds to finish, then copy the appropriate sections out of the output (trimming the timestamps). If I were more familiar with the Pipelines features, I'm pretty sure I could make four parallel jobs inside the same build that ran the tests on each branch, export the logs as artifacts, then auto-assemble the email at the end. I plan to do that soon, but I'm still keeping a close eye on the results to see when and where failures occur.

Thanks, -Stolee

[1] https://dev.azure.com/git/git/_build?definitionId=5
Previous: Junio C HamanoNext: brian m. carlson
Message 3 of 4 in “Git Test Coverage Report (Saturday, Oct 27)”
  1. Derrick StoleeOct 27, 2018
  2. Junio C HamanoOct 27, 2018
  3. Derrick StoleeOct 27, 2018
  4. brian m. carlsonOct 27, 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.