new file mode 100644
@@ -0,0 +1,31 @@
+# Format
+#
+# A file can specify a `DEFAULTS` section which will be used when any hint is missing a field.
+# A fallback value of `.*` is used for any field not specified in the hint or `DEFAULTS`:
+# The hints themselves are organized by `test suite`, with a list for each hint.
+#
+# See README for full file format specification.
+#
+# DEFAULTS
+# key: value
+# test_suite_name_1:
+# - key: hint_1 value
+# key2: hint_1 value2
+# - key: hint_2 value
+# key2: hint_2 value2
+# key3: hint_2 value3
+# test_suite_name_2
+# - key: hint_3 value
+# key2: hint_3 value2
+
+DEFAULTS:
+ series: impish
+ source: linux-riscv
+ cloud: metal
+
+boot:
+ - version: 5.11.0.*
+ test-case: log_check
+ arch: riscv
+ state: FLAKY
+ comment: 'LP: #1905728 Issued caused by CONFIG_STRICT_KERNEL_RWX and some sections, likely init sections, carrying both text and data.'
During the boot test the log_check unit test is reporting a failure, because warnings like the following are found in dmesg: WARNING: CPU: 4 PID: 1 at arch/riscv/mm/ptdump.c:231 note_page+0x254/0x25a WARNING: CPU: 3 PID: 1 at arch/riscv/mm/ptdump.c:231 note_page+0x254/0x25a WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:231 note_page+0x254/0x25a WARNING: CPU: 3 PID: 1 at arch/riscv/mm/ptdump.c:231 note_page+0x254/0x25a This is a known / won't fix problem in riscv (see LP: #1905728), so we can safely hint the test for now. BugLink: https://bugs.launchpad.net/bugs/1905728 Signed-off-by: Andrea Righi <andrea.righi@canonical.com> --- impish-linux-riscv.yaml | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 impish-linux-riscv.yaml