From: Anthony Green <green@moxielogic.com>
To: libffi-discuss <libffi-discuss@sourceware.org>
Subject: CI changes and test failures on ppc64le-linux-gnu
Date: Wed, 16 Oct 2019 20:22:00 -0000 [thread overview]
Message-ID: <CACxje5_5Lxv5xNFGL7nGx45zgN_raHDWHZLpt+26D53Q4f+Fcw@mail.gmail.com> (raw)
I've been working on adding additional architecture support to our
travis-ci tests and, to that end, I just committed a patch to test on 32-
and 64-bit ARM and ppc64le Linux systems as well as using foreign fedora
container images emulated with qemu.
https://github.com/libffi/libffi/commit/825b2a359468af8bf3570a5a0695e8b805c5446f
The builder images are defined in a new project here:
https://github.com/libffi/ci-build-containers
One of the tricks to get this working was to split the testing of different
optimization levels into different build jobs (so as to not to exceed the
build timeout limits on travis). So now you can set
LIBFFI_TEST_OPTIMIZATIONS="-O2" and 'make check' will only test that
optimization level. Travis runs multiple build jobs in parallel, so this
seems like a good strategy.
Test results look good, with the exception of some ppc64le failures on the
struct-related tests. Unfortunately, I'm unable to run gdb in this kind of
emulated environment, so I'd appreciate it if somebody could have a look.
I also just noticed that Nov 12 will mark the 5th anniversary of the last
libffi release. It would be nice to release a new one on that day this
year. There are still a number of patches in the queue that I'll try to
dig into again, but I would appreciate help!
Thanks!
AG
next reply other threads:[~2019-10-16 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 20:22 Anthony Green [this message]
2019-10-21 12:16 ` Anthony Green
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=CACxje5_5Lxv5xNFGL7nGx45zgN_raHDWHZLpt+26D53Q4f+Fcw@mail.gmail.com \
--to=green@moxielogic.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).