Re: libffi 3.3 release candidate 1
Anthony Green <[email protected]>
| Newsgroups | gmane.linux.debian.ports.superh,gmane.comp.lib.ffi.general,gmane.linux.debian.ports.68k |
|---|---|
| Message-ID | <CAAs=koj3HU08uxx36809NcPYe33xvEjUDsLwJc_9R8V4tbr9Zg@mail.gmail.com> |
Hey John, I was using that one, but I haven't been able to connect to it today, so I took it out for now. I'll try again later. libffi doesn't see a ton of activity, so I predict a light load... but this an experiment and we'll see how it goes! AG On Thu, Oct 31, 2019 at 4:32 PM John Paul Adrian Glaubitz <[email protected]> wrote: > > Hi Anthony! > > > On Oct 31, 2019, at 9:06 PM, Anthony Green <[email protected]> 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 > > -- Anthony Green <[email protected]> Senior Principal Solutions Architect, Financial Services +1 647 477-3809