public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: bugs on exotic archs
Date: Mon, 12 May 2014 20:45:18 +0200	[thread overview]
Message-ID: <201405122045.18801.sweet_f_a@gmx.de> (raw)

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
  fdisk/bsd
%endif

%ifarch ppc
  fdisk/gpt
%endif

%ifarch armv6l armv7l aarch64
  misc/setarch
%endif

%ifarch armv6l aarch64
  fdisk/gpt
  fdisk/oddinput
  fdisk/sunlabel
  misc/ionice
  misc/swaplabel
  kill/name
  kill/print_pid
%endif

%ifarch aarch64
  utmpdump
%endif

You can get the build logs and test diffs here
https://build.opensuse.org/package/show/home:rudi_m:branches:Base:System/util-linux
(The build status usually shows "success" because I've marked these 
tests "known-fail" to be noticed when we would add more bugs.)

cu,
Rudi

             reply	other threads:[~2014-05-12 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 18:45 Ruediger Meier [this message]
2014-05-13  8:23 ` bugs on exotic archs Karel Zak
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=201405122045.18801.sweet_f_a@gmx.de \
    --to=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