public inbox for
 help / color / mirror / Atom feed
From: Gary Benson <>
To: Radovan Birdic <>
Subject: Re: Test 'valid/test-corpus' fails for 32-bit architectures
Date: Tue, 30 May 2017 19:48:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <7d79-5921f880-1b-16986660@154324279>

Hi Radovan,

Radovan Birdic wrote:
> Package libi8x fails on Debian for all 32-bit endian architectures during testing:
> Full build log for mipsel:
> Binary files 'test_deref/0015-0001' and 'test_deref/0011-0001' from test folder 0.0.4 cause a problem.
> Does it make sense to you to threat these tests like the same tests from 0.0.3 version?
> I have created and attached a patch that handles these tests.
> With this patch package builds successfully on my local mips, mipsel and i386 machines.
> Could you please look at this?

I'm not around til June 6 but I don't see a problem treating the tests
like 0.0.3 for now, just to get it building. I don't remember the
details but I think it's a corner case.


  reply	other threads:[~2017-05-30 19:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 20:28 Radovan Birdic
2017-05-30 19:48 ` Gary Benson [this message]
2017-06-05 12:37   ` Gary Benson
2017-06-05 13:19     ` Gary Benson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).