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

Re: unit tests / cirrus ci fails

From
Fabian Stelzer <fs@gigacodes.de>
Date
Jul 9, 2021, 16:04 UTC
Message-ID
<db030e49-edb0-8f4b-0e51-a89b2a4a47a8@gigacodes.de>
In-Reply-To
<YOhmAGig//yfABWv@danh.dev>
On 09.07.21 17:06, Đoàn Trần Công Danh wrote:
Show 14 quoted lines
> On 2021-07-09 15:31:01+0200, Fabian Stelzer <fs@gigacodes.de> wrote:
>> Hi,
>> i'm having a issue with a failing test on my pull request.
>> https://github.com/git/git/pull/1041/checks?check_run_id=3028222798
>>
>> I have added a bunch of new tests and they fail on the freebsd12 test that's
>> run via gitgitgadget.
>> Is there any way to enable verbose / debug output on these or a simple way
>> to run tests manually in the same environment?
> I don't know about cirrus CI, but, skimming over the log, it run into
> fatal error after skipping t4202.71, I think the bashism in
> "test_lazy_prereq GPGSSH" is the culprit.
>
> "|&" in "ssh_version=$(ssh-keygen -Y find-principals |& grep -q "unknown option")"

Thanks, that was indeed (part of) the problem. The new tests themselves are failing now and i have no idea why on freebsd :/ Are there detailed logs publicly available from the CI runs? Or is my only option to set up a freebsd 12 vm to try to replicate this? Does the ci simply run "make test" or is there another mechanism involved?

Previous: Đoàn Trần Công DanhNext: Philippe Blain
Message 3 of 4 in “unit tests / cirrus ci fails”
  1. Fabian StelzerJul 9, 2021
  2. Đoàn Trần Công DanhJul 9, 2021
  3. Fabian StelzerJul 9, 2021
  4. Philippe BlainJul 10, 2021

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.