From 57eb17a8ca9350afa89b625463190be23c63c649 Mon Sep 17 00:00:00 2001 From: Inaky Perez-Gonzalez Date: Tue, 3 Jan 2017 10:01:52 -0800 Subject: [PATCH] tests/kernel/stackprot: 'fatal fault' is not a failure By default, when a 'fatal fault' message is seen in the output of any testcase, it is consider an inmediate fatal condition and the test case is aborted. However, this testcase is provoking the situation to verify the condition is caught. This, it shall NOT be considered a fatal fault and the default overriden to allow it to proceed. This was done in the legacy testcases and now is moved to this testcase, ported from legacy. Change-Id: Icac6cf55cae2ffd9b071e9dd1f35918b7b30de5e Signed-off-by: Inaky Perez-Gonzalez --- tests/kernel/stackprot/defaults.tc | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 tests/kernel/stackprot/defaults.tc diff --git a/tests/kernel/stackprot/defaults.tc b/tests/kernel/stackprot/defaults.tc new file mode 100644 index 00000000000..c0eb6df9589 --- /dev/null +++ b/tests/kernel/stackprot/defaults.tc @@ -0,0 +1,6 @@ +# +# This TC will force a fatal fault, as it is testing it. Don't error +# if we find it (cancel out the default setting in root's defaults.tc +# that will consider a testcase toast if a fatal fault is found +# +# ^eval console-rx %(console)s::pass [Ff]atal fault in