From: Fabian Stelzer <fs@gigacodes.de>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: unit tests / cirrus ci fails
Date: Fri, 9 Jul 2021 18:04:01 +0200 [thread overview]
Message-ID: <db030e49-edb0-8f4b-0e51-a89b2a4a47a8@gigacodes.de> (raw)
In-Reply-To: <YOhmAGig//yfABWv@danh.dev>
On 09.07.21 17:06, Đoàn Trần Công Danh wrote:
> 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?
next prev parent reply other threads:[~2021-07-09 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 13:31 unit tests / cirrus ci fails Fabian Stelzer
2021-07-09 15:06 ` Đoàn Trần Công Danh
2021-07-09 16:04 ` Fabian Stelzer [this message]
2021-07-10 20:42 ` Philippe Blain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db030e49-edb0-8f4b-0e51-a89b2a4a47a8@gigacodes.de \
--to=fs@gigacodes.de \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).