public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: David Chinner <dgc@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: qa 166 failure on f8 kernel
Date: Tue, 07 Aug 2007 23:28:48 -0500	[thread overview]
Message-ID: <46B94680.3070405@sandeen.net> (raw)
In-Reply-To: <20070808041920.GK52011508@sgi.com>

David Chinner wrote:

> That could be done, but will break on 64k page size machines ;)
> 
> Perhaps the filter needs to use `getconf PAGE_SIZE` to filter the
> output down:
> 
> ia64:
> 
> % getconf PAGE_SIZE
> 16384
> 
> x86_64:
> 
> % getconf PAGE_SIZE
> 4096
> 
> So the written extent sizes are output as a multiple of
> page size rather than basic blocks....


yeah, computing all the numbers for the filter seemed nasty.

Maybe just a dumbed-down filter that expects

written
unwritten
written
unwritten
written

would be sufficient for this test.

--- 166.orig    2007-08-07 23:19:33.391317217 -0500
+++ 166 2007-08-07 23:21:11.111409407 -0500
@@ -31,9 +31,9 @@
 {
        $AWK_PROG '/[0-9]/ {
                if ($7)
-                       print $1, $2, "XX..YY", "AG", "(AA..BB)", $6, $7;
+                       print $7
                else
-                       print $1, $2, "XX..YY", "AG", "(AA..BB)", $6;
+                       print "no flags"
        }'
 }

--- 166.out.orig        2007-08-07 23:21:25.299244961 -0500
+++ 166.out     2007-08-07 23:21:45.706131763 -0500
@@ -1,6 +1,6 @@
 QA output created by 166
-0: [0..31]: XX..YY AG (AA..BB) 32
-1: [32..127]: XX..YY AG (AA..BB) 96 10000
-2: [128..159]: XX..YY AG (AA..BB) 32
-3: [160..223]: XX..YY AG (AA..BB) 64 10000
-4: [224..255]: XX..YY AG (AA..BB) 32
+no flags
+10000
+no flags
+10000
+no flags


-Eric

  reply	other threads:[~2007-08-08  4:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  1:39 qa 166 failure on f8 kernel Eric Sandeen
2007-08-08  2:56 ` David Chinner
2007-08-08  2:58   ` Eric Sandeen
2007-08-08  4:08     ` David Chinner
2007-08-08  4:11       ` Eric Sandeen
2007-08-08  4:16         ` Eric Sandeen
2007-08-08  4:19         ` David Chinner
2007-08-08  4:28           ` Eric Sandeen [this message]
2007-08-08  4:57             ` Barry Naujok
2007-08-08  5:00               ` Eric Sandeen
2007-08-08 13:13       ` Christoph Hellwig
2007-08-08 13:17         ` David Chinner
2007-08-08  4:13   ` Alex Elder
     [not found]     ` <D59801BCA402F5418C040937230AF7E00B9A8E@mtv-amer002e--3.americas.sgi.c om>
2007-08-08  5:47       ` nscott
2007-08-08  4:19 ` Barry Naujok
2007-08-08  4:18   ` Eric Sandeen

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=46B94680.3070405@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=dgc@sgi.com \
    --cc=xfs@oss.sgi.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