From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Anthony Green <green@moxielogic.com>
Cc: Matthias Klose <doko@ubuntu.com>,
libffi-discuss <libffi-discuss@sourceware.org>,
Debian m68k <debian-68k@lists.debian.org>,
debian-superh@lists.debian.org
Subject: Re: libffi 3.3 release candidate 1
Date: Thu, 31 Oct 2019 20:32:00 -0000 [thread overview]
Message-ID: <772E071F-528C-49B7-9C1E-F3829D45BAD9@physik.fu-berlin.de> (raw)
In-Reply-To: <CACxje59QxG0GR4yTyvopUt6ZbifgwFdycFuQ+TS5989JbkNX7w@mail.gmail.com>
Hi Anthony!
> On Oct 31, 2019, at 9:06 PM, Anthony Green <green@moxielogic.com> wrote:
>
>
> I've figured out a way to use the GCC compile farm (https://cfarm.tetaneutral.net/) with travis-ci so real hardware builds/tests can participate in the travis-ci testing process.
(...)
> If anybody is willing to give me ssh access to additional gear, I'd be happy to add them to the mix.
The GCC compile farm also includes a SPARC T5 LDOM which runs Debian unstable which we set up. You should be able to use that as well.
Although I’m not so sure if it’s okay to run CI tests on the compile farm for every commit as the resources are limited.
Adrian
next prev parent reply other threads:[~2019-10-31 20:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:17 Anthony Green
2019-10-25 10:08 ` Matthias Klose
2019-10-25 10:29 ` John Paul Adrian Glaubitz
2019-10-25 14:41 ` Andreas Schwab
2019-10-25 14:44 ` John Paul Adrian Glaubitz
2019-10-25 18:32 ` Andreas Schwab
2019-10-25 18:37 ` John Paul Adrian Glaubitz
2019-10-25 19:04 ` Andreas Schwab
2019-10-25 19:07 ` John Paul Adrian Glaubitz
2019-10-26 11:35 ` Anthony Green
2019-10-26 12:54 ` Anthony Green
2019-10-31 19:49 ` Anthony Green
2019-10-31 20:32 ` John Paul Adrian Glaubitz [this message]
[not found] ` <CAAs=koj3HU08uxx36809NcPYe33xvEjUDsLwJc_9R8V4tbr9Zg@mail.gmail.com>
2019-10-31 22:16 ` John Paul Adrian Glaubitz
2019-11-01 8:01 ` John Paul Adrian Glaubitz
2019-11-01 22:24 ` John Paul Adrian Glaubitz
2019-11-08 9:21 ` Matthias Klose
2019-11-08 14:28 ` Anthony Green
2019-11-09 16:04 ` Matthias Klose
2019-11-09 17:46 ` Anthony Green
2019-11-10 16:22 ` Matthias Klose
2019-11-26 8:39 ` Matthias Klose
2019-11-26 23:25 ` Anthony Green
2019-11-27 7:54 ` Matthias Klose
2019-11-27 9:28 ` Anthony Green
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=772E071F-528C-49B7-9C1E-F3829D45BAD9@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--cc=debian-superh@lists.debian.org \
--cc=doko@ubuntu.com \
--cc=green@moxielogic.com \
--cc=libffi-discuss@sourceware.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 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).