From: Philippe Blain <levraiphilippeblain@gmail.com>
To: "Fabian Stelzer" <fs@gigacodes.de>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: unit tests / cirrus ci fails
Date: Sat, 10 Jul 2021 16:42:55 -0400 [thread overview]
Message-ID: <dba84da7-f6ec-37b3-4322-378af9249d54@gmail.com> (raw)
In-Reply-To: <db030e49-edb0-8f4b-0e51-a89b2a4a47a8@gigacodes.de>
Hi Fabian,
Le 2021-07-09 à 12:04, Fabian Stelzer a écrit :
> 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?
the logs should be accessible on the "Checks" tab of your PR
if you are logged into GitHub. But I don't think there is more
to see than what's shown there.
> 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?
>
I managed to log into the Cirrus-CI FreeBSD VM using tunshell [1].
I found out about it at [2]. Here's the commit in my fork [3]
0. Create a Cirrus-CI account and give it access to your fork of Git
1. Create the tunshell session at [1]
2. Run the local script on your local host
3. Copy the remote script in '.cirrus.yml' in you branch
(ex. as the first step of the "test_script:" section), commit and push to GitHub
4. wait for the build to start on Cirrus and the tunshell client on your machine
should connect you to the VM.
5. Go to /tmp/cirrus-ci-build in the VM to find the git.git checkout
Caveat: your public IP will be viewable in the Cirrus log.
[1] https://tunshell.com/go
[3] https://github.com/phil-blain/git/commit/b47d803ee1ba83100702cb80c93e18c74d787dce
[2] https://github.com/cirruslabs/cirrus-ci-docs/issues/432
prev parent reply other threads:[~2021-07-10 20:43 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
2021-07-10 20:42 ` Philippe Blain [this message]
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=dba84da7-f6ec-37b3-4322-378af9249d54@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=congdanhqx@gmail.com \
--cc=fs@gigacodes.de \
--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).