From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: bugs on exotic archs
Date: Tue, 13 May 2014 10:23:49 +0200 [thread overview]
Message-ID: <20140513082349.GL8951@x2.net.home> (raw)
In-Reply-To: <201405122045.18801.sweet_f_a@gmx.de>
On Mon, May 12, 2014 at 08:45:18PM +0200, Ruediger Meier wrote:
> Hi,
>
> If somebody of you wants to do some sports...
>
> Here I have a list of failing tests on certain architectures. If you own
> such system you may want to confirm and fix the one or the other issue.
> IMO most interesting are the fdisk failures on ppc and ppc64 and
> utmpdump on aarch64 which are IMO real bugs. The other ones might be
> bugs in the test suite or broken build hosts.
>
> Failing test on certain archs:
>
> %ifarch ppc ppc64
> hexdump
this is not a bug, but the hexdump test disadvantage -- the output
may be different on big-endian if the output is composed from more input bytes.
> fdisk/bsd
BSD disklabel location depends on arch
> %endif
>
> %ifarch ppc
> fdisk/gpt
this is strange
> %endif
>
> %ifarch armv6l armv7l aarch64
> misc/setarch
setarch: armv7l: Unrecognized architecture
> %endif
>
> %ifarch armv6l aarch64
> fdisk/gpt
> fdisk/oddinput
> fdisk/sunlabel
Unsupported ioctl: cmd=0xffffffff801c0204 (1c)
> misc/ionice
qemu: Unsupported syscall: 314
ionice: ioprio_set failed: Function not implemented
> misc/swaplabel
Unsupported ioctl: cmd=0xffffffff801c0204 (1c)
> kill/name
> kill/print_pid
kill: cannot find process "naYZRDhfqEzs9bP".
> %endif
>
> %ifarch aarch64
> utmpdump
> %endif
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-05-13 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:45 bugs on exotic archs Ruediger Meier
2014-05-13 8:23 ` Karel Zak [this message]
2014-05-13 13:36 ` Ruediger Meier
2014-05-29 15:01 ` Ruediger Meier
2014-05-29 15:25 ` [PATCH] tests: fix fdisk/bsd for big endian systems Ruediger Meier
2014-05-29 17:32 ` Ruediger Meier
2014-05-29 17:52 ` Ruediger Meier
2014-06-09 11:02 ` Karel Zak
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=20140513082349.GL8951@x2.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.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