From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59518 invoked by alias); 4 Apr 2018 21:05:26 -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 59509 invoked by uid 89); 4 Apr 2018 21:05:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=HTo:U*libffi-discuss, anthony, Anthony, HTo:U*green X-HELO: einhorn-mail.in-berlin.de Received: from einhorn-mail.in-berlin.de (HELO einhorn-mail.in-berlin.de) (217.197.80.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Apr 2018 21:05:23 +0000 X-Envelope-From: doko@ubuntu.com Received: from [192.168.178.37] (ip5f5bd68c.dynamic.kabel-deutschland.de [95.91.214.140]) (authenticated bits=0) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w34L48Xj032023 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 4 Apr 2018 23:04:09 +0200 Subject: Re: libffi 3.3 release candidate 0 To: Anthony Green , libffi-discuss@sourceware.org References: From: Matthias Klose Message-ID: Date: Wed, 04 Apr 2018 21:05:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2018/txt/msg00014.txt.bz2 On 02.04.2018 14:54, Anthony Green wrote: > libffi 3.3 release candidate 0 is available for testing... > > > https://github.com/libffi/libffi/releases/download/v3.3-rc0/libffi-3.3-rc0.tar.gz > > https://github.com/libffi/libffi/releases/tag/v3.3-rc0 > > I'm still aiming for a final release before the end of May. The purpose of > the release candidate is to test the packaging (make sure the release > tarball is complete) and collect initial test results for platforms not > included in the regular travis and appveyor CI systems. > > Speaking of CI systems, any additional CI integrations or test > configurations (gcc on windows? running the tests on macos? etc) would be > particularly welcome. And, along those lines, I'd like to give special > thanks to github user @fwg for fixing the appveyor msvc CI testing > yesterday. here are the build logs for the Debian architectures (although not all architectures are yet build, maybe check the "old" builds for that). https://buildd.debian.org/status/package.php?p=libffi&suite=experimental armel, armhf, ia64, m68k, powerpcspe, riscv64, sh4, x32, kfreebsd-amd64, kfreebsd-i386: - no test results yet. Please see the URL above for recent builds, or look in the OLD column. amd64, arm64, ppc64el, hppa, powerpc: - all tests pass i386 (this is really i686): - libffi.bhaible/test-call.c, libffi.bhaible/test-callback.c FAIL - # of expected passes 6765 - # of unexpected failures 691 hurd-i386: - libffi.bhaible/test-callback.c FAIL - # of expected passes 6768 - # of unexpected failures 688 mips: - libffi.bhaible/test-callback.c FAIL - # of expected passes 2868 - # of unexpected failures 8 mips64el: - libffi.call/cls_longdouble_va.c FAIL - # of expected passes 2872 - # of unexpected failures 4 mipsel: - libffi.bhaible/test-callback.c FAIL - # of expected passes 2868 - # of unexpected failures 8 s390x: - libffi.bhaible/test-call.c FAIL - # of expected passes 3076 - # of unexpected failures 24 ppc64: - libffi.bhaible/test-callback.c FAIL - # of expected passes 2804 - # of unexpected failures 72 sparc64: - libffi.bhaible/test-call.c FAIL - # of expected passes 3076 - # of unexpected failures 24