From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Ed Maste <emaste@freefall.freebsd.org>
Cc: git@vger.kernel.org, Ed Maste <emaste@freebsd.org>
Subject: Re: [PATCH] ci: add Cirrus-CI config for FreeBSD CI
Date: Tue, 26 Nov 2019 00:44:19 +0000 [thread overview]
Message-ID: <20191126004419.GE2404748@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20191125203740.72249-1-emaste@freefall.freebsd.org>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On 2019-11-25 at 20:37:40, Ed Maste wrote:
> From: Ed Maste <emaste@freebsd.org>
>
> Cirrus-CI is relatively unique among hosted CI providers in supporting
> FreeBSD (in addition to Linux, Windows, and macOS). Add a Cirrus-CI
> config to facilitate building and testing on FreeBSD.
>
> Signed-off-by: Ed Maste <emaste@freebsd.org>
I'm all for automated testing on FreeBSD, but we would need someone to
triage and address any failures reasonably quickly. Is that something
you'd be okay with doing, or is there someone else who would be okay
with doing that?
> ---
> 6 i18n tests are currently failing and need investigation.
> Example result: https://cirrus-ci.com/task/5394512637067264
> Test log: https://api.cirrus-ci.com/v1/task/5394512637067264/logs/test.log
Could we fix these issues first so we don't have CI suddenly start
failing?
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-11-26 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 20:37 [PATCH] ci: add Cirrus-CI config for FreeBSD CI Ed Maste
2019-11-26 0:44 ` brian m. carlson [this message]
2019-11-26 13:31 ` Ed Maste
2019-11-27 14:01 ` Ed Maste
2019-11-27 15:17 ` Ed Maste
2019-12-20 2:11 ` [PATCH v2] CI: add FreeBSD CI support via Cirrus-CI Ed Maste
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191126004419.GE2404748@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=emaste@freebsd.org \
--cc=emaste@freefall.freebsd.org \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.