From: Radovan Birdic <radovan.birdic@rt-rk.com>
To: infinity@sourceware.org
Subject: Tests fail for big endian architectures
Date: Wed, 26 Apr 2017 11:15:00 -0000 [thread overview]
Message-ID: <059ab0b9-c57a-bf1d-1a24-468f60fccc58@rt-rk.com> (raw)
Hi,
Package libi8x fails on Debian for all big endian architectures during
testing:
> make check-TESTS
> FAIL: exec/test-deref
> FAIL: exec/test-factorial
> ========================================
> libi8x 0.0.2: tests/test-suite.log
> ========================================
>
> # TOTAL: 2
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 2
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: exec/test-deref
> =====================
>
> exec/test-deref.c:168: <testnote>[0x2b]: Corrupt note
> FAIL exec/test-deref (exit status: 1)
>
> FAIL: exec/test-factorial
> =========================
>
> exec/test-factorial.c:92:
corpus/i8c/0.0.3/32be/test_loops/test_basic/0001-0001[0x39]: Corrupt note
> FAIL exec/test-factorial (exit status: 1)
>
>
============================================================================
> Testsuite summary for libi8x 0.0.2
>
============================================================================
> # TOTAL: 2
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 2
> # XPASS: 0
> # ERROR: 0
>
============================================================================
Full build log for mips:
https://buildd.debian.org/status/fetch.php?pkg=libi8x&arch=mips&ver=0.0.2-2&stamp=1486258076&raw=0
Any suggestions?
Regards,
Radovan
next reply other threads:[~2017-04-26 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 11:15 Radovan Birdic [this message]
2017-04-26 12:38 ` Gary Benson
2017-04-28 9:52 ` Radovan Birdic
2017-04-28 13:58 ` 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=059ab0b9-c57a-bf1d-1a24-468f60fccc58@rt-rk.com \
--to=radovan.birdic@rt-rk.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).