All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Maste <emaste@freebsd.org>
To: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: [PATCH] ci: add Cirrus-CI config for FreeBSD CI
Date: Wed, 27 Nov 2019 09:01:56 -0500	[thread overview]
Message-ID: <CAPyFy2DLYHZnzrwA27JQRxGkpf=+Z8ND-6AX3+oepAL+RNwQGg@mail.gmail.com> (raw)
In-Reply-To: <20191126004419.GE2404748@camp.crustytoothpaste.net>

On Mon, 25 Nov 2019 at 19:44, brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>
> 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?

Renato Botelho <garga@freebsd.org> is the maintainer of the devel/git
port/package on FreeBSD and has now also joined this list and offered
to help triage and address issues.

> Could we fix these issues first so we don't have CI suddenly start
> failing?

After some further investigation I believe these tests are technically
invalid but work with glibc because of its looser requirements. I've
sent a patch (t4210: skip i18n tests that don't work on FreeBSD) to
address the failures.

  parent reply	other threads:[~2019-11-27 17:48 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
2019-11-26 13:31   ` Ed Maste
2019-11-27 14:01   ` Ed Maste [this message]
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='CAPyFy2DLYHZnzrwA27JQRxGkpf=+Z8ND-6AX3+oepAL+RNwQGg@mail.gmail.com' \
    --to=emaste@freebsd.org \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /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.