From: Gary Benson <gbenson@redhat.com>
To: Radovan Birdic <Radovan.Birdic@rt-rk.com>
Cc: infinity@sourceware.org, Matthias Klose <doko@ubuntu.com>
Subject: Re: Test 'valid/test-corpus' fails for 32-bit architectures
Date: Mon, 05 Jun 2017 12:37:00 -0000 [thread overview]
Message-ID: <CAHegJi+nHQP_kaD06=vMUiDBNwEQ5T1rvUrOe6zS8xK8D-0ptA@mail.gmail.com> (raw)
In-Reply-To: <CAHegJiLRsRWvKh4D8eDhu=5Rkfi2moQLKQ5GA-qCRhKA74iziQ@mail.gmail.com>
(Cc-ing Doko, because I think he's emailing me about the same thing)
Gary Benson wrote:
> Radovan Birdic wrote:
> > Package libi8x fails on Debian for all 32-bit endian architectures during testing:
> ...
> > Full build log for mipsel:
> > https://buildd.debian.org/status/fetch.php?pkg=libi8x&arch=mipsel&ver=0.0.3-1&stamp=1493727519&raw=0
> >
> > 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.
I've added this to the roadmap, to be looked at for the next release
(which is imminent)
https://wekan.sergiodj.net/b/kMNy6KavRQaFkRzmM/infinity/8Kpao6JKZbfjwpic2
Cheers,
Gary
--
https://infinitynotes.org/
next prev parent reply other threads:[~2017-06-05 12:37 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
2017-06-05 12:37 ` Gary Benson [this message]
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:
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='CAHegJi+nHQP_kaD06=vMUiDBNwEQ5T1rvUrOe6zS8xK8D-0ptA@mail.gmail.com' \
--to=gbenson@redhat.com \
--cc=Radovan.Birdic@rt-rk.com \
--cc=doko@ubuntu.com \
--cc=infinity@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).