From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81731 invoked by alias); 31 Oct 2019 19:49:27 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 81398 invoked by uid 89); 31 Oct 2019 19:49:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 spammy=H*Ad:U*libffi-discuss, anthony, Anthony, U*doko X-HELO: mail-lj1-f194.google.com Received: from mail-lj1-f194.google.com (HELO mail-lj1-f194.google.com) (209.85.208.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 31 Oct 2019 19:49:05 +0000 Received: by mail-lj1-f194.google.com with SMTP id g3so1816666ljl.11 for ; Thu, 31 Oct 2019 12:48:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=moxielogic-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=29hnpbPjvHYjSz9ISCzaINXPaWHmo9DXwWSk0aVGxsg=; b=eBXixaYxsHmWNdGQlWEMGjeS9mnxfChQUS5gxFItTx92fGmjdlMlRM9PG6Q+PsolbQ J1lZuCu1fOscO2wLynX9JSN2ZbtCXjAXpz1x2fOZJOPk4znyUlSY/2ScPVorjGFPxZx+ hwgtQaZq1GmHqDtk5a9CW3DJ5rXP3TXvCiULyXTN5JWLO0tyep3U/c9stRhYKB0tflUD 8M9PZ55NQBMJIQuaoRFL/fY4khUMQ/Dm3Pds0hrvSBEHRoNYqI7OVUgNUI49uJc+HaUN mCKC3EneA5U/zAWMCDXRpW06qnIb5TuaTfxnr4waXbYass3nP61V7ZLHd83l11X9sBol s0yw== MIME-Version: 1.0 References: <34f2c328-d879-71f9-2c60-34045d452f38@ubuntu.com> In-Reply-To: From: Anthony Green Date: Thu, 31 Oct 2019 19:49:00 -0000 Message-ID: Subject: Re: libffi 3.3 release candidate 1 To: Matthias Klose Cc: libffi-discuss , Debian m68k , debian-superh@lists.debian.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00051.txt.bz2 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. AG On Sat, Oct 26, 2019 at 8:53 AM Anthony Green wrote: > On Fri, Oct 25, 2019 at 6:08 AM Matthias Klose 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 >> https://buildd.debian.org/status/package.php?p=libffi&suite=experimental >> >> 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. > > AG > > >