public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: libffi test results with trunk 20171020
Date: Sun, 22 Oct 2017 08:49:00 -0000	[thread overview]
Message-ID: <049e7714-d22c-b146-f05d-77f58b9bc02e@ubuntu.com> (raw)

I had another test build of libffi trunk; the individual build logs can be seen
at https://buildd.debian.org/status/package.php?p=libffi&suite=experimental

The base system is glibc-2.23, binutils-2.29 and GCC 7.2.  Not including the
failures here for architectures with many failing test cases.

architectures without failures:
x86_64, i686, aarch64, hppa, mips, mipsel, powerpc, ppc64, ppc64el, s390x,
sparc64, kfreebsd-amd64, kfreebsd-i686,

I have no test results for m68k, powerpcspe and sh4 because a Debian port
maintainer decides not to run the tests during the build. I'll work around that
next time.

I see test failures on armel, armhf and mips64el.  on The Hurd the testsuite
gets killed. x86_64-linux-gnux32 doesn't build (issue #306).

Matthias


arm-linux-gnueabi (armv4t, soft float):
# of expected passes		2045
# of unexpected failures	105

arm-linux-gnueabihf (armv7, hard-float, thumb mode)
# of expected passes		2142
# of unexpected failures	49

mips64el-unknown-linux-gnuabi64
Running ../../testsuite/libffi.call/call.exp ...
FAIL: libffi.call/cls_longdouble_va.c -W -Wall -Wno-psabi -O0 output pattern test
FAIL: libffi.call/cls_longdouble_va.c -W -Wall -Wno-psabi -O2 output pattern test
FAIL: libffi.call/cls_longdouble_va.c -W -Wall -Wno-psabi -O3 output pattern test
FAIL: libffi.call/cls_longdouble_va.c -W -Wall -Wno-psabi -Os output pattern test
FAIL: libffi.call/cls_longdouble_va.c -W -Wall -Wno-psabi -O2
-fomit-frame-pointer output pattern test
# of expected passes		1955
# of unexpected failures	5
# of unsupported tests		28

alpha-linux-gnu
# of expected passes		2235
# of expected failures		5

i686-pc-gnu (Hurd):
Running ../../testsuite/libffi.call/call.exp ...
/bin/bash: line 3: 27502 Killed                  runtest --tool $tool --srcdir
$srcdir
Makefile:412: recipe for target 'check-DEJAGNU' failed
make[3]: *** [check-DEJAGNU] Error 1


                 reply	other threads:[~2017-10-22  8:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=049e7714-d22c-b146-f05d-77f58b9bc02e@ubuntu.com \
    --to=doko@ubuntu.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).