From: Bryan Schumaker <bjschuma@netapp.com>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Thomas Haynes <thomas@netapp.com>,
linux-nfs@vger.kernel.org
Subject: Re: Patched up cthon source?
Date: Tue, 25 Jan 2011 08:43:25 -0500 [thread overview]
Message-ID: <4D3ED37D.6020606@netapp.com> (raw)
In-Reply-To: <4D3DFE40.1070605@panasas.com>
On 01/24/2011 05:33 PM, Benny Halevy wrote:
> this is a problem with the version of nroff on newer distributions.
My version of groff (1.21) is splitting the error into two lines, so I am using the following patch.
Bryan
--- a/general/runtests.wrk
+++ a/general/runtests.wrk
@@ -88,6 +88,12 @@
$TIME nroff < nroff.tbl > nroff.out 2>> nroff.time || cat nroff.time
$TIME nroff < nroff.tbl > nroff.out 2>> nroff.time || cat nroff.time
rm nroff.out nroff.tbl
+# Filter excessive noise from GNU nroff. Should be harmless for other
+# versions of nroff.
+egrep -v '^warning:.*$' <nroff.time >nroff.new
+mv -f nroff.new nroff.time
+egrep -v '^ table wider.*$' <nroff.time >nroff.new
+mv -f nroff.new nroff.time
set -e
./stat nroff.time
set +e
next prev parent reply other threads:[~2011-01-25 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 22:19 Patched up cthon source? Thomas Haynes
2011-01-24 22:24 ` Chuck Lever
2011-01-24 22:33 ` Benny Halevy
2011-01-24 23:01 ` Jim Rees
2011-01-24 23:32 ` Thomas Haynes
2011-01-25 13:43 ` Bryan Schumaker [this message]
2011-01-25 14:56 ` Jeff Layton
2011-01-25 15:38 ` Trond Myklebust
2011-01-25 15:46 ` peter.staubach
2011-01-25 15:53 ` Jeff Layton
[not found] ` <20110125095649.446212fd-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-02-07 19:13 ` Jim Rees
2011-02-07 22:00 ` Jeff Layton
2011-01-24 22:50 ` sfaibish
2011-01-25 9:46 ` DENIEL Philippe
2011-01-25 17:05 ` Steve Dickson
2011-01-25 21:36 ` Halevy, Benny
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=4D3ED37D.6020606@netapp.com \
--to=bjschuma@netapp.com \
--cc=bhalevy@panasas.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=thomas@netapp.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 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 NNTP newsgroup(s).