[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libffi 3.3 release candidate 1

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.  The trick was to write a web service (https://github.com/libffi/cfarm-test-libffi) that travis-ci will curl to for specific platforms, and it is responsible for ssh'ing into the appropriate compile farm box for testing.  It seems to work well, so I've replaced the aarch64 qemu testing with real aarch64, as well as added ppc64le and mips64el linux tests.  Here's some sample results: https://travis-ci.org/libffi/libffi/builds/605684679

If anybody is willing to give me ssh access to additional gear, I'd be happy to add them to the mix.


On Sat, Oct 26, 2019 at 8:53 AM Anthony Green <green@moxielogic.com> wrote:
On Fri, Oct 25, 2019 at 6:08 AM Matthias Klose <doko@ubuntu.com> wrote:On 24.10.19 13:16, Anthony Green wrote:
> libffi 3.3 release candidate 1 is available for testing...
> https://github.com/libffi/libffi/releases/download/v3.3-rc1/libffi-3.3-rc1.tar.gz
> https://github.com/libffi/libffi/releases/tag/v3.3-rc1

test results from

without test failures: amd64, armel, armhf, arm64, mips64el, mipsel, ppc64el,
s390x, alpha, hppa, ia64, kfreebsd-amd64, powerpc. ppc64, riscv64, sparc64, x32

I didn't look at XPASSes.

The XPASSes are related to an ABI incompatibility problem in GCC that has since been fixed.  



Reply to: