luv-test-parser: Add timestamp field to schema

Including a timestamp field in the output of the test results is useful
for gathering performance data, i.e. how long did each unit test take to
run.

Increment the schema version to v1.1 while retaining backwards
compatibility with v1.0. This allows parsers to be upgraded piece-meal
to the new schema.

Upgrading parsers individually is very powerful, since we don't
currently have any way to gather timestamp data from BITS, and can't
update the BITS parser to v1.1 of the schema right now.

Cc: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
luv: Add timestamp to luv-parser-fwts

Modify luv-parser-fwts to get a timestamp on
frontline of each unittest when fwts executed

Changes will meet the schema 1.1 version updated
in the luv-test-parser file by Matt Fleming and now the
format looks like this
"1.1 timestamp fwts unittest RESULT 1 0 0 0"

Patch provides the clear understanding of how much
time did each of the unittests take to run

Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
luv: Add timestamp to luv-parser-efivarfs

Modify luv-parser-efivarfs to get a timestamp on
frontline of each unittest when efivarfs executed

Changes will meet the schema 1.1 version updated
in the luv-test-parser file by Matt Fleming and now the
format looks like this
"1.1 timestamp efivarfs unittest RESULT 1 0 0 0"

Patch provides the clear understanding
of how much time did each of the unittests take to run

Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
fwts: Fix luv-parser-fwts INFO results

The INFO results currently printed for fwts fail to emit interesting
parts of the log results, due to the following expression in awk,

  substring($0, index($0, $8))

I'm not at all sure what the purpose of printing the substring starting
at $8 was, but needless to say that weird things happen if there aren't
8 words on the input line (some of the fwts INF messages are less than 8
words).

With this change, instead of seeing the following in the parsed
directory,

 1.1 <timestamp> fwts cpufreq INFO P-State tests.
 1.1 <timestamp> fwts cpufreq INFO system, this test steps through
 1.1 <timestamp> fwts cpufreq INFO that the BIOS

we now see this instead,

 1.1 <timestamp> fwts cpufreq INFO Test 1 of 1: CPU P-State tests.
 1.1 <timestamp> fwts cpufreq INFO For each processor in the system, this test steps through
 1.1 <timestamp> fwts cpufreq INFO the various frequency states (P-states) that the BIOS

Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
luv: Add timestamp to luv-parser-chipsec

Modify luv-parser-chipsec to get a timestamp on frontline of each
unittest when chipsec is executed. This provides a better understanding
of how much time each of the unit tests take to run.

Changes meets the schema 1.1 version updated in the luv-test-parser
file by Matt Fleming (commit 3d6102e137422f884327290f81abd1004f61318e)
and now the format looks like this:
"1.1 timestamp chipsec unittest RESULT 1 0 0 0"

Additionally, flush stdout manually from gawk to improve interaction
with the serial output. Further detail can be found in commit
72d7be73daecfbd30050d1d465ab8c0c89d1d262.

Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
CHIPSEC: Enable the CHIPSEC test suite

The CHIPSEC test suite was disabled in the  commit #af66ed38bad4
because of hang/freeze issues when running on ASUS P8H67-M LE
hardware as described in issue #7.

Chipsec is know to work well on various platform based on
Broadwell and  Haswell. It also ran correctly on HP Elite Book
8470p.

But users are starting to ask for this test suite to be included
in the LUV. There's no sense in disabling it entirely if it hangs
on a specific platform as described in issue #7. So let's enable
CHIPSEC for users test out!

Cc: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
LUV v1.2-rc2