public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Matthias Klose <doko@ubuntu.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: test results on many platforms
Date: Sun, 22 Oct 2017 14:58:00 -0000	[thread overview]
Message-ID: <4194955.7kWH6ZJhqX@omega> (raw)
In-Reply-To: <98b4d355-2a30-26d7-29a2-831338ea76cf@ubuntu.com>

Hi Matthias,

> could you repeat these tests with libffi trunk?

No, I won't do that.

1) When I test something, I want to test the build infrastructure with it.
   Therefore I take a tarball with 'configure' file as input.

2) You have to understand that it takes time to run tests on dozens of
   machines, for 65 ABIs, and review the results.

I am not the only person who can run these tests:
  - The test suite is at a public place.[1]
  - Many of the platforms are available to anyone, through QEMU emulation.[2]

But if you provide a (release or prerelease) tarball and I see signs that
some of the bugs might be fixed, I might find the time to verify that these
bug are indeed fixed.

> could these new tests added to the libffi testsuite itself?

If you can accommodate a GPLed testsuite in the MIT/BSD-licensed libffi,
you can do that already now.

Otherwise, I can ask my collaborator if it would be ok with him to relicense
this testsuite under the MIT/BSD license used by libffi.

Bruno

[1] https://haible.de/bruno/gnu/libffi-testsuite.tar.gz
[2] http://git.savannah.gnu.org/gitweb/?p=libffcall.git;a=tree;f=porting-tools/emulation

  reply	other threads:[~2017-10-22 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21 18:31 Bruno Haible
2017-10-22  8:12 ` Matthias Klose
2017-10-22 14:58   ` Bruno Haible [this message]
2017-10-22 18:28 ` Kaz Kylheku (libffi)
2017-10-22 20:33   ` small return types Bruno Haible
2017-10-22 21:38     ` Kaz Kylheku (libffi)
2017-10-25  5:18     ` Tom Tromey

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=4194955.7kWH6ZJhqX@omega \
    --to=bruno@clisp.org \
    --cc=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).