[PATCH v1] fwts: Update fwts to v18.03.00
by Gayatri Kammela
Update FWTS to version v18.03.00
Signed-off-by: Gayatri Kammela <gayatri.kammela(a)intel.com>
---
meta-luv/recipes-core/fwts/fwts_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/fwts/fwts_git.bb b/meta-luv/recipes-core/fwts/fwts_git.bb
index 1b1f75177d1f..227d171b6345 100644
--- a/meta-luv/recipes-core/fwts/fwts_git.bb
+++ b/meta-luv/recipes-core/fwts/fwts_git.bb
@@ -4,9 +4,9 @@ HOMEPAGE = "https://wiki.ubuntu.com/Kernel/Reference/fwts"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://src/main.c;beginline=1;endline=16;md5=31da590f3e9f3bd34dcdb9e4db568519"
-PV = "V18.02.00+git${SRCPV}"
+PV = "V18.03.00+git${SRCPV}"
-SRCREV = "f0afecfc709d9970c7cebee352cd5154db3e52f7"
+SRCREV = "4f35a54a4098d794cb50fba15530c53a8c05d9f1"
SRC_URI = "git://kernel.ubuntu.com/hwe/fwts.git \
file://luv-parser-fwts \
"
--
2.7.4
3 years, 6 months
[PATCH] chipsec: Remove do_make_scripts
by Megha Dey
Poky removes do_make_scripts() and puts the functionality in a separate
recipe. (Commit bb5a8acd: 'make-mod-scripts: change how some kernel
module tools are built')
Thus, removing the do_make_script from chipsec recipe as well.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-core/chipsec/chipsec_git.bb | 5 -----
1 file changed, 5 deletions(-)
diff --git a/meta-luv/recipes-core/chipsec/chipsec_git.bb b/meta-luv/recipes-core/chipsec/chipsec_git.bb
index c596c50..c2c977e 100644
--- a/meta-luv/recipes-core/chipsec/chipsec_git.bb
+++ b/meta-luv/recipes-core/chipsec/chipsec_git.bb
@@ -30,11 +30,6 @@ inherit python-dir
inherit distutils
inherit luv-test
-addtask make_scripts after do_patch before do_compile
-do_make_scripts[lockfiles] = "${TMPDIR}/kernel-scripts.lock"
-do_make_scripts[depends] += "virtual/kernel:do_shared_workdir"
-do_make_scripts[deptask] = "do_populate_sysroot"
-
S = "${WORKDIR}/git"
export INC = "-I${STAGING_INCDIR}/${PYTHON_DIR}"
--
1.9.1
3 years, 6 months
[PATCH] luv: Update LINUXLIBCVERSION
by Megha Dey
As we have bumped the linux-libc-headers to 4.15, we need to update this
variable as well.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/conf/distro/luv.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-luv/conf/distro/luv.conf b/meta-luv/conf/distro/luv.conf
index 633d424..9f244dd 100644
--- a/meta-luv/conf/distro/luv.conf
+++ b/meta-luv/conf/distro/luv.conf
@@ -4,7 +4,7 @@ DISTRO_VERSION = "2.2-dev"
TCLIBCAPPEND = ""
PREFERRED_PROVIDER_virtual/kernel = "linux-luv"
-LINUXLIBCVERSION = "4.14"
+LINUXLIBCVERSION = "4.15"
LAYER_CONF_VERSION ?= "6"
--
1.9.1
3 years, 6 months
[PATCH] qemu: Update to 2.11.1
by Megha Dey
Poky bumped QEMU to v2.11.1. Update LUV append for QEMU accordingly.
No functional changes were made.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-devtools/qemu/qemu_2.11.0.bbappend | 2 --
meta-luv/recipes-devtools/qemu/qemu_2.11.1.bbappend | 2 ++
2 files changed, 2 insertions(+), 2 deletions(-)
delete mode 100644 meta-luv/recipes-devtools/qemu/qemu_2.11.0.bbappend
create mode 100644 meta-luv/recipes-devtools/qemu/qemu_2.11.1.bbappend
diff --git a/meta-luv/recipes-devtools/qemu/qemu_2.11.0.bbappend b/meta-luv/recipes-devtools/qemu/qemu_2.11.0.bbappend
deleted file mode 100644
index ea0fc2f..0000000
--- a/meta-luv/recipes-devtools/qemu/qemu_2.11.0.bbappend
+++ /dev/null
@@ -1,2 +0,0 @@
-RDEPENDS_append_class-native_x86 = " ovmf"
-RDEPENDS_append_class-native_x86-64 = " ovmf"
diff --git a/meta-luv/recipes-devtools/qemu/qemu_2.11.1.bbappend b/meta-luv/recipes-devtools/qemu/qemu_2.11.1.bbappend
new file mode 100644
index 0000000..ea0fc2f
--- /dev/null
+++ b/meta-luv/recipes-devtools/qemu/qemu_2.11.1.bbappend
@@ -0,0 +1,2 @@
+RDEPENDS_append_class-native_x86 = " ovmf"
+RDEPENDS_append_class-native_x86-64 = " ovmf"
--
1.9.1
3 years, 6 months
[PATCH v3 0/4] luv-test-manager: Multiple fixes to first_boot logic
by Gayatri Kammela
Hi,
This patch series 3 focus on fixing issues related to first_boot file.
1) Create first_boot file only if reboot_tests parameter is configured.
2) Parse the results to the first_boot as and when done, to get accurate test
results to avoid duplicates.
3) Use a signature flag as an indication that if the first_boot file is old, remove it.
4) Lastly, don't reuse the first_boot results unless it is the same host and
first_boot is still on the disk.
Changes since v1:
1) Add 3 more patches to the series.
Changes since v2:
1) Added checks to see if the first_boot file exists before performing any operations
2) Added an additional check to remove the first_boot file
3) Added a signature flag which is only set when one or more reboot_tests are configured
4) Append the test suites names to the first_boot and then sync
Gayatri Kammela (4):
luv-test-manager: Create first_boot only if any reboot_tests are
enabled
luv-test-manager: Fix the issue to parse accurate results to
first_boot
luv-test-manager: Add a signature flag to indicate the reboot tests
and to remove the first_boot file
luv-test-manager: Identify the host to reuse the first_boot results
.../luv-test/luv-test/luv-test-manager | 80 +++++++++++++++-------
1 file changed, 55 insertions(+), 25 deletions(-)
--
2.7.4
3 years, 6 months
[PATCH 0/9] Display the severity of failed test cases - Part 1
by Ricardo Neri
Hi,
This is the first merge-worthy version of my patchset to add a severity
marking to failed test cases. My initial submission can be found here [1].
I have made several updates based on the received feedback. Please refer
to the change log.
I have split the series. The first half deals with the implementation of
rendering the severity in the HTML report and querying JSON files. The
second half (to be sent soon) deals with updating each of the test suites
to provide a severity for each test case.
== Why?
LUV now ships 7 different test suites. Some test suites include hundreds
of test cases. Thus, we could possibly have tens of failed test cases. It
can be overwhelming.
In order to help users to decide on which failed test cases focus their
attention, it is useful to indicate the severity of failed test cases.
== The rules and looks
In the HTML test report, failed test cases are decorated with one icon
that deplicts the severity of the failure. These icons have three shades
of red. Redder icons decorate more sever failures. Likewise, in the text
report and the console output, failed test cases are prepended with one
to three exclamation points. The looks can be seen here [2] and [3].
Patches 1 through 5 deal with the look and feel of the depiction of
severity.
== How?
Some test suites already classify failures by severity. An example of this
is FWTS. For this case, all we have to do is take such severity and include
it in the parser that LUV uses to generate the report. This is done in
patch 6.
Some other test suites do not include a classification. In such a case, we
can generate our own. An example of this is CHIPSEC. For this, I generated
a JSON file that contains metadata of each test case (for now, only
severity). The scripts that parses the results look at this metadata to
incorporate severity in the parsed results.
Adding a JSON file seems a good idea because it can be extended in the
future to include more metadata for test cases (e.g., an URL for more info,
advice, etc). For this to work, I wrote a recipe to bring jq into LUV.
jq is a command-line JSON processor.
Patches 6 through 9 provide the underlying functionality that individual
parsers can use to parse their respective JSON files.
== Changes since RFC
+ Depict severity by icons with different shades of grade, instead of
icons
+ Insert icons after the test case name and not before
+ Remove the exclamation point after failed test caes
+ Add margin and spacing to the legend.
== Where can I get this code?
The two series of patches can be retrieved from here:
https://github.com/intel/luv-yocto.git rneri/severity_of_errors_v2
This work is based on Megha's branch for-luv-2.3-rc1
Thanks and BR,
Ricardo
[1]. https://lists.01.org/pipermail/luv/2018-February/002545.html
[2]. https://imagebin.ca/v/3vnx6Uiv5tvs
[3]. https://imagebin.ca/v/3rpzIGrRgiSD
Ricardo Neri (9):
luv-test-parser: Simplify print of test case name and status
luv-test-parser: Print severity of a test case
luv-test: Install icons for HTML test report
luv-test-parser: Show the level of severity of test cases
luv-test-parser: Update schemas to include test case severity
meta-luv: Add a recipe for jq
luv-test: Add a library of awk functions for test parsing
luv-test: Update path to helper files in installed parsers
luv-test: Optionally install a JSON file for the parser
meta-luv/classes/luv-test.bbclass | 13 ++++
meta-luv/recipes-bsp/bits/bits/luv-parser-bits | 2 +-
.../chipsec/chipsec/luv-parser-chipsec | 4 +-
.../efivarfs/efivarfs-test/luv-parser-efivarfs | 4 +-
meta-luv/recipes-core/fwts/fwts/luv-parser-fwts | 2 +-
meta-luv/recipes-core/jq/jq_git.bb | 20 ++++++
.../luv-parser-kernel-efi-warnings | 6 +-
meta-luv/recipes-core/luv-test/luv-test.bb | 18 ++++-
.../recipes-core/luv-test/luv-test/icon_fail1.png | Bin 0 -> 464 bytes
.../recipes-core/luv-test/luv-test/icon_fail2.png | Bin 0 -> 452 bytes
.../recipes-core/luv-test/luv-test/icon_fail3.png | Bin 0 -> 459 bytes
.../luv-test/luv-test/icon_failunk.png | Bin 0 -> 536 bytes
.../recipes-core/luv-test/luv-test/luv-css-styles | 5 ++
.../luv-test/luv-test/luv-test-manager | 23 +++++++
.../recipes-core/luv-test/luv-test/luv-test-parser | 76 ++++++++++++++++-----
.../luv-test/luv-test/luv-test-parser-lib | 23 +++++++
meta-luv/recipes-core/ndctl/ndctl/luv-parser-ndctl | 8 +--
.../pstore-test/pstore-test/luv-parser-pstore-test | 4 +-
18 files changed, 174 insertions(+), 34 deletions(-)
create mode 100644 meta-luv/recipes-core/jq/jq_git.bb
create mode 100644 meta-luv/recipes-core/luv-test/luv-test/icon_fail1.png
create mode 100644 meta-luv/recipes-core/luv-test/luv-test/icon_fail2.png
create mode 100644 meta-luv/recipes-core/luv-test/luv-test/icon_fail3.png
create mode 100644 meta-luv/recipes-core/luv-test/luv-test/icon_failunk.png
create mode 100644 meta-luv/recipes-core/luv-test/luv-test/luv-test-parser-lib
--
2.7.4
3 years, 6 months
[PATCH 0/9] Display the severity of failed test cases - Part 2
by Ricardo Neri
This is the second of two series that add functionality to display the
severity of failed test cases in LUV. The first half of the series
can be found here [1]. You can referer to the cover letter of the first
series for motivation and details of implementation.
The main goal of this series is to assign all the test cases in each test
suite a level of severity. Some test suites already provide this and all
we have to do is update the parsers. For other test suites, a severity is
assigned in the form of a JSON file. I would really appreciate if you could
look at these JSON files and decide if you agree on the assigned severity.
The same change is repeate for CHIPSEC, BITS, efivarfs-test, ndctl and
pstore-test.
Our parser for kernel error (kernel-efi-warnings) does not use a JSON file.
Instead, the severity is embedded in the script used to inspect the
severity of test cases.
FWTS already provides a severity. Thus, the parser was only updated to
report such severity.
The two series of patches can be retrieved from here:
https://github.com/intel/luv-yocto.git rneri/severity_of_errors_v2
This work is based on Megha's branch for-luv-2.3-rc1
Thanks and BR,
Ricardo
[1]. https://lists.01.org/pipermail/luv/2018-March/002637.html
Ricardo Neri (9):
fwts: Report the test cases' severity in parsed output
chipsec: Report the test cases' severity in parsed output
bits: Report the test cases' severity in parsed output
efivarfs-test: Report the test cases' severity in parsed output
ndctl: Report the test cases' severity in parsed output
pstore-tests: Report the test cases' severity in parsed output
kernel-efi-warnings: runner: Emit the severity of a test case
kernel-efi-warnings: Assign severity to test cases
kernel-efi-warnings: parser: Report the test cases' severity
meta-luv/recipes-bsp/bits/bits/bits.json | 26 ++++++++
meta-luv/recipes-bsp/bits/bits/luv-parser-bits | 10 ++-
meta-luv/recipes-bsp/bits/bits_git.bb | 2 +
meta-luv/recipes-core/chipsec/chipsec/chipsec.json | 74 ++++++++++++++++++++++
.../chipsec/chipsec/luv-parser-chipsec | 17 +++--
meta-luv/recipes-core/chipsec/chipsec_git.bb | 5 +-
meta-luv/recipes-core/efivarfs/efivarfs-test.bb | 4 +-
.../efivarfs/efivarfs-test/efivarfs.json | 34 ++++++++++
.../efivarfs/efivarfs-test/luv-parser-efivarfs | 9 ++-
meta-luv/recipes-core/fwts/fwts/luv-parser-fwts | 28 +++++++-
.../kernel-efi-warnings/kernel-efi-warnings | 55 +++++++++++-----
.../luv-parser-kernel-efi-warnings | 16 ++++-
meta-luv/recipes-core/ndctl/ndctl/luv-parser-ndctl | 6 +-
meta-luv/recipes-core/ndctl/ndctl/ndctl.json | 22 +++++++
meta-luv/recipes-core/ndctl/ndctl_git.bb | 3 +
meta-luv/recipes-core/pstore-test/pstore-test.bb | 4 +-
.../pstore-test/pstore-test/luv-parser-pstore-test | 8 ++-
.../pstore-test/pstore-test/pstore-test.json | 42 ++++++++++++
18 files changed, 330 insertions(+), 35 deletions(-)
create mode 100644 meta-luv/recipes-bsp/bits/bits/bits.json
create mode 100644 meta-luv/recipes-core/chipsec/chipsec/chipsec.json
create mode 100644 meta-luv/recipes-core/efivarfs/efivarfs-test/efivarfs.json
create mode 100644 meta-luv/recipes-core/ndctl/ndctl/ndctl.json
create mode 100644 meta-luv/recipes-core/pstore-test/pstore-test/pstore-test.json
--
2.7.4
3 years, 6 months
[PATCH] luv-test: Use weak assignments for parsers' variables
by Ricardo Neri
The variables LUV_TEST_ARGS, LUV_TEST and LUV_TEST_LOG_PARSER are
intended to be set by children of this class. Thus, use weak assignments
to make this fact evident.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
---
meta-luv/classes/luv-test.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-luv/classes/luv-test.bbclass b/meta-luv/classes/luv-test.bbclass
index 289aeaa..5685cd0 100644
--- a/meta-luv/classes/luv-test.bbclass
+++ b/meta-luv/classes/luv-test.bbclass
@@ -3,10 +3,10 @@
# This file will automatically generate and install a test runner
# script for a package.
-LUV_TEST_ARGS = ""
-LUV_TEST = "${PN}"
+LUV_TEST_ARGS ?= ""
+LUV_TEST ?= "${PN}"
-LUV_TEST_LOG_PARSER = ""
+LUV_TEST_LOG_PARSER ?= ""
# The installation directory of test runner scripts and log parsers
runnerdir = "${sysconfdir}/luv/tests"
--
2.7.4
3 years, 6 months
[PATCH] luv-test: Simplify usage of variables
by Ricardo Neri
Yes, you can have too many variables. Reduce the number of variables in
this class. Having too many variables makes this file rather hard to read.
Furthermore, after this simplification, paths and variable names are
specified in a manner that is similar to other Poky recipes. This further
improves readability.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
---
meta-luv/classes/luv-test.bbclass | 18 +++++++-----------
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/meta-luv/classes/luv-test.bbclass b/meta-luv/classes/luv-test.bbclass
index 1d0f781..289aeaa 100644
--- a/meta-luv/classes/luv-test.bbclass
+++ b/meta-luv/classes/luv-test.bbclass
@@ -9,24 +9,20 @@ LUV_TEST = "${PN}"
LUV_TEST_LOG_PARSER = ""
# The installation directory of test runner scripts and log parsers
-RUNNER_PATH = "${sysconfdir}/luv/tests"
-PARSER_PATH = "${sysconfdir}/luv/parsers"
+runnerdir = "${sysconfdir}/luv/tests"
+parserdir = "${sysconfdir}/luv/parsers"
FILES_${PN} += "${RUNNER_PATH}/${PN} ${PARSER_PATH}/${PN}"
do_install_append() {
- runner_dir="${D}${RUNNER_PATH}"
- install -d $runner_dir
-
- log_dir="${D}${PARSER_PATH}"
- install -d $log_dir
+ install -d ${D}${runnerdir}
+ install -d ${D}${parserdir}
if [ ! -z ${LUV_TEST_LOG_PARSER} ]; then
- parser="${PARSER_PATH}/${PN}"
- install -m 755 ${WORKDIR}/${LUV_TEST_LOG_PARSER} ${D}${parser}
+ install -m 755 ${WORKDIR}/${LUV_TEST_LOG_PARSER} ${D}${parserdir}/${PN}
fi
- cat > ${runner_dir}/${PN} <<EOF
+ cat > ${D}${runnerdir}/${PN} <<EOF
#!/bin/sh
#
# This is an automatically generated test runner script that is invoked
@@ -37,5 +33,5 @@ do_install_append() {
${LUV_TEST} ${LUV_TEST_ARGS}
EOF
- chmod +x ${runner_dir}/${PN}
+ chmod +x ${D}${runnerdir}/${PN}
}
--
2.7.4
3 years, 6 months
[PATCH] meta-luv: parsers: Include the 'aborts' field in the RESULT tag
by Ricardo Neri
The RESULT tag of the LUV parsing schemas for test results looks like
this:
RESULT [passes] [failures] [aborts] [skips] [warnings]
Thus, the ordering of these five fields is crucial to parse the test
results correctly.
The parsers for BITS, efivarfs, kernel-efi-warnings and pstore-tests fail
to report the full five needed fields. This has the effect of leaving the
[warnings] field empty. Furthermore, in some specific cases, the skipped
test cases are reported as aborts.
When not used, insert a '0' in the abort field to both complete the
number of required fields and report each field in the correct
position.
Cc: Gayatri Kammela <gayatri.kammela(a)intel.com>
Cc: Sai Praneeth Prakhya <sai.praneeth.prakhya(a)intel.com>
Cc: Megha Dey <megha.dey(a)intel.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
---
meta-luv/recipes-bsp/bits/bits/luv-parser-bits | 2 +-
meta-luv/recipes-core/efivarfs/efivarfs-test/luv-parser-efivarfs | 4 ++--
.../kernel-efi-warnings/luv-parser-kernel-efi-warnings | 6 +++---
.../recipes-core/pstore-test/pstore-test/luv-parser-pstore-test | 4 ++--
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/meta-luv/recipes-bsp/bits/bits/luv-parser-bits b/meta-luv/recipes-bsp/bits/bits/luv-parser-bits
index a7507fe..4f59ac6 100644
--- a/meta-luv/recipes-bsp/bits/bits/luv-parser-bits
+++ b/meta-luv/recipes-bsp/bits/bits/luv-parser-bits
@@ -13,7 +13,7 @@ awk '/\=\=\=/ {
parsing_tests = 1;
prev_test = test;
} else {
- printf "1.0 bits %s RESULT %d %d %d 0\n", prev_test, passes,
+ printf "1.0 bits %s RESULT %d %d 0 %d 0\n", prev_test, passes,
fails, skips;
passes = 0; fails = 0; skips =0;
printf ("1.0 bits %s END\n", prev_test);
diff --git a/meta-luv/recipes-core/efivarfs/efivarfs-test/luv-parser-efivarfs b/meta-luv/recipes-core/efivarfs/efivarfs-test/luv-parser-efivarfs
index fbb0e21..18d8d45 100644
--- a/meta-luv/recipes-core/efivarfs/efivarfs-test/luv-parser-efivarfs
+++ b/meta-luv/recipes-core/efivarfs/efivarfs-test/luv-parser-efivarfs
@@ -37,14 +37,14 @@ awk '/\-\-\-\-/ {
/\[PASS\]/ {
"date +%H:%M:%S:%N" | getline current_time;
close ("date +%H:%M:%S:%N")
- printf ("1.1 %s efivarfs %s RESULT 1 0 0 0 \n", current_time, test);
+ printf ("1.1 %s efivarfs %s RESULT 1 0 0 0 0 \n", current_time, test);
fflush("");
}
/\[FAIL\]/ {
"date +%H:%M:%S:%N" | getline current_time;
close ("date +%H:%M:%S:%N")
- printf ("1.1 %s efivarfs %s RESULT 0 1 0 0 \n", current_time, test);
+ printf ("1.1 %s efivarfs %s RESULT 0 1 0 0 0 \n", current_time, test);
fflush("");
}
diff --git a/meta-luv/recipes-core/kernel_efi_warnings/kernel-efi-warnings/luv-parser-kernel-efi-warnings b/meta-luv/recipes-core/kernel_efi_warnings/kernel-efi-warnings/luv-parser-kernel-efi-warnings
index 01984d8..e1fd7f2 100644
--- a/meta-luv/recipes-core/kernel_efi_warnings/kernel-efi-warnings/luv-parser-kernel-efi-warnings
+++ b/meta-luv/recipes-core/kernel_efi_warnings/kernel-efi-warnings/luv-parser-kernel-efi-warnings
@@ -17,17 +17,17 @@ awk '/Test:/ {
}
/PASS/ {
- printf ("1.0 kernel-efi-warnings %s RESULT 1 0 0 0\n", test);
+ printf ("1.0 kernel-efi-warnings %s RESULT 1 0 0 0 0\n", test);
fflush("");
}
/SKIP/ {
- printf ("1.0 kernel-efi-warnings %s RESULT 0 0 1 0\n", test);
+ printf ("1.0 kernel-efi-warnings %s RESULT 0 0 0 1 0\n", test);
fflush("");
}
/FAIL/ {
- printf ("1.0 kernel-efi-warnings %s RESULT 0 1 0 0\n", test);
+ printf ("1.0 kernel-efi-warnings %s RESULT 0 1 0 0 0\n", test);
fflush("");
}
diff --git a/meta-luv/recipes-core/pstore-test/pstore-test/luv-parser-pstore-test b/meta-luv/recipes-core/pstore-test/pstore-test/luv-parser-pstore-test
index 2263203..5aad6c3 100644
--- a/meta-luv/recipes-core/pstore-test/pstore-test/luv-parser-pstore-test
+++ b/meta-luv/recipes-core/pstore-test/pstore-test/luv-parser-pstore-test
@@ -25,12 +25,12 @@ awk -v reboot_test=${REBOOT_TEST} '/ing/ {
}
/ok/ {
- printf ("1.2 pstore-tests %d %s RESULT 1 0 0 0\n", reboot_test, test);
+ printf ("1.2 pstore-tests %d %s RESULT 1 0 0 0 0\n", reboot_test, test);
fflush("");
}
/FAIL/ {
- printf ("1.2 pstore-tests %d %s RESULT 0 1 0 0\n", reboot_test, test);
+ printf ("1.2 pstore-tests %d %s RESULT 0 1 0 0 0\n", reboot_test, test);
fflush("");
}
--
2.7.4
3 years, 6 months