Re: qa 166 failure on f8 kernel

Eric Sandeen
2007-08-08T04:28:48Z

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