Very rough storage validation matrix draft
Kamil Paral
kparal at redhat.com
Mon Mar 17 08:14:50 UTC 2014
> On Fri, 2014-03-14 at 04:47 -0400, Kamil Paral wrote:
> > > the result columns used to be for different filesystems. Now they're for
> > > different platforms - x86 BIOS, x86 UEFI, and ARM.
> >
> > This is a bit unclear for me.
> >
> > Does "x86 BIOS" mean "x86 BIOS _or_ x86_64 BIOS", and "x86 UEFI" mean
> > "x86_64 UEFI"?
>
> I picked x86 to be "bitness-independent", the point being x86 not ARM.
x86 is unfortunately often used to refer to 32b arch only. But I see no other term which could be used to mean x86(_32)+x86_64, so let's leave it like that.
> We could have x32 BIOS, x64 BIOS, x64 UEFI, but I was trying to keep the
> numbers down. Have we ever found a case where storage behaved
> differently between x32 and x64? I can't recall one.
I can't either, and even if I did, I don't think it would justify the result number explosion. Storage is storage, arch is usually completely irrelevant.
When we're at it, why do we have both i686 and x86_64 at "Device tests"? A single results column for x86 should be enough. Same reasoning.
More information about the test
mailing list