Kernel tests

[Jon Stanley]

So I have to admit that I saw that Fedora badges were now being
awarded for kernel testing, so I went ahead and submitted my results.
In the process, I made a few observations (both on the process and on
the tests themselves):

First from the process standpoint, has it been thought about to make
the process easier for testers than going to a webpage and uploading
results manually? Could we make it even easier by somehow asking for a
FAS identity and then uploading it?

As for the test content itself, the test header has no information as
to what hardware it is running on, which for performance tests
matters, and possibly for some functionality tests as well (vendors
with buggy firmware, etc). I'm not sure what format patches are
preferred in, but there's a branch hw-info of
git://githuib.com/jds2001/kernel-tests that has this. A log header now
looks like:

Date: Mon Aug 11 16:39:26 EDT 2014
Test set: default
Kernel: 3.16.0-1.fc22.x86_64
Release: Fedora release 20 (Heisenbug)
Result: PASS
Failed Tests: None
System Manufaturer: Hewlett-Packard
System Product Name: h8-1070t
BIOS Version: 7.05
BIOS Release Date: 05/18/2011
Processor: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
gcc version: gcc-4.8.3-1.fc20.x86_64
glibc version: glibc-2.18-12.fc20.x86_64
Virtualization: none
============================================================

There might be other useful things to include as well, these are some
things that I can think of from a "possible to provide in a singe
line" output. Note that since some users might be concerned about
giving out lots of (potentially sensitive - think things like serial
number/asset tag), I didn't include a full dump of dmidecode, though
that really would be the holy grail of information that I'd want (and
lspci, lsmod, etc).

Another test that would be worthwhile that I don't think I'm smart
enough to write on my own is whether AutoNUMA is working as intended.
This would of course require NUMA hardware (or booting a system with
fake NUMA).