From: Jeff Garzik <jeff@garzik.org>
To: Project Hail <hail-devel@vger.kernel.org>
Cc: Rick Jones <rick.jones2@hp.com>, Pete Zaitcev <zaitcev@redhat.com>
Subject: chunkd and ppc[64] progress
Date: Mon, 10 Aug 2009 14:19:49 -0400 [thread overview]
Message-ID: <4A8064C5.30707@garzik.org> (raw)
I didn't want the endian issue to linger for too long, so I went ahead
and applied the s/32/64/ portion of Pete's chunkd endian fix proposed
patch (commit 468e7e393a6e12a410e1ab788c0beeb751c0225e).
As mentioned, I created type-safe static inline wrappers for the GLib
endian conversion functions. These were added to cld in
include/cld-private.h, and to chunkd in include/chunk-private.h.
The Fedora ppc/ppc64 build definitely proceeds, getting farther but not
100% of the way. Here's the koji scratch build I just performed:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1595728
build log that shows ppc build failure:
http://koji.fedoraproject.org/koji/getfile?taskID=1595729&name=build.log
which shows
[...]
test failed on line 37
FAIL: large-object
lotsa-objects PUT: 2104.63 ops/sec
lotsa-objects syncing...
test failed on line 58
FAIL: lotsa-objects
build log that shows ppc64 build failure:
http://koji.fedoraproject.org/koji/getfile?taskID=1595731&name=build.log
which shows
[...]
large-object PUT: 111.06 MB/sec
chunkd[7298]: client ::ffff:127.0.0.1 error NoSuchKey
chunkd[7298]: client ::ffff:127.0.0.1 error InvalidArgument
chunkd[7298]: client ::ffff:127.0.0.1 connected
test failed on line 118
FAIL: large-object
chunkd[7298]: client ::ffff:127.0.0.1 connected
chunkd[7298]: client ::ffff:127.0.0.1 error NoSuchKey
test failed on line 41
FAIL: lotsa-objects
But hey... it gets farther than my previous chunkd builds on ppc, and
Pete definitely found an endian conversion bug.
Jeff
reply other threads:[~2009-08-10 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A8064C5.30707@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=zaitcev@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.