From f81cdf9d3a475b6135c0951d1c7169f226164baf Mon Sep 17 00:00:00 2001
From: Petri Latvala <petri.latvala@intel.com>
Date: Tue, 13 Nov 2018 13:22:51 +0200
Subject: runner: Handle escaped characters from kmsg

Characters in kernel logs, when read from /dev/kmsg, are escaped as
\xNN if they are not between 32 and 127 of if they are "\". Decode
what we can when creating results.json.

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
 runner/json_tests_data/dmesg-escapes/joblist.txt | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 runner/json_tests_data/dmesg-escapes/joblist.txt

(limited to 'runner/json_tests_data/dmesg-escapes/joblist.txt')

diff --git a/runner/json_tests_data/dmesg-escapes/joblist.txt b/runner/json_tests_data/dmesg-escapes/joblist.txt
new file mode 100644
index 00000000..81f914a7
--- /dev/null
+++ b/runner/json_tests_data/dmesg-escapes/joblist.txt
@@ -0,0 +1 @@
+successtest first-subtest
-- 
cgit v1.2.3