From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, Andreas Henriksson <andreas@fatal.se>
Subject: Re: [PATCH] tests: fix fdisk/bsd for alpha
Date: Wed, 16 Mar 2016 16:27:10 +0100 [thread overview]
Message-ID: <201603161627.10907.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20160316131107.4orceajqir34wavj@ws.net.home>
On Wednesday 16 March 2016, Karel Zak wrote:
> On Wed, Mar 16, 2016 at 12:37:41PM +0100, Karel Zak wrote:
> > On Wed, Mar 16, 2016 at 01:40:44AM +0100, Ruediger Meier wrote:
> > > BTW it was a bad idea to use md5sum. In case of failure it
> > > would be much easier to debug hexdump diffs. Now it's nearly
> > > impossible to collect all these exotic hexdumps.
> >
> > I'll try to prepare a new test with hexdump, PPC[64] LE/BE should
> > not be a problem. The rest we can gather later.
>
> Done, the last missing is Aplha (with special fields in the
> label...).
Thanks! I was really to lazy to refactor this one.
> The original md5 based test is still in the tree to make a way how
> to verify Alpha output. Maybe it's overkill and we can remove the
> test. Not sure.
>
> Test it, try it, send patches ;)
Hehe, maybe the only alpha machine on this planet is this Debian build
host:
https://buildd.debian.org/status/package.php?p=util-linux&suite=experimental
We can wait until Adreas updates the package and copy/paste it from the
log like I've got that md5sum;)
BTW there are only two more test failures left on sparc:
FAILED (fdisk/id)
--- /<<PKGBUILDDIR>>/tests/expected/fdisk/id
+++ /<<PKGBUILDDIR>>/tests/output/fdisk/id
@@ -1,3 +1,5 @@
Initialize empty image
Create MBR with ID=0x1
-Disk identifier: 0x00000001
Create MBR with ID=0x2
-Disk identifier: 0x00000002
FAILED (fdisk/mbr-nondos-mode)
--- /<<PKGBUILDDIR>>/tests/expected/fdisk/mbr-nondos-mode
+++ /<<PKGBUILDDIR>>/tests/output/fdisk/mbr-nondos-mode
@@ -1,189 +1,203 @@
Initialize empty image
8f4e33f3dc3e414ff94e5fb6905cba8c mbr-nondos-mode.img
Create new DOS partition table
-4e23561dcb81678bb1bd678722c7cbb7 mbr-nondos-mode.img
+8f4e33f3dc3e414ff94e5fb6905cba8c mbr-nondos-mode.img
And we could disable setarch's uname26 test because
# glibc requires kernel >= 3.0, thus setarch --uname-2.6 fails
# on platforms without VDSO
cu,
Rudi
next prev parent reply other threads:[~2016-03-16 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 0:40 [PATCH] tests: fix fdisk/bsd for alpha Ruediger Meier
2016-03-16 11:37 ` Karel Zak
2016-03-16 13:11 ` Karel Zak
2016-03-16 15:27 ` Ruediger Meier [this message]
2016-03-17 13:33 ` Karel Zak
2016-03-17 21:52 ` Ruediger Meier
2016-03-18 14:36 ` Karel Zak
2016-03-22 11:04 ` Ruediger Meier
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=201603161627.10907.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=andreas@fatal.se \
--cc=kzak@redhat.com \
--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