Chore: Keep records of error code and its corresponding output messages

integration-tests/project-folder/sources/meta-error/recipes-error/error/compilation-python-function.bb

@@ -0,0 +1,6 @@
+# ERROR: [file-path]: Error in compiling python function in [file-path], line [line-number]:
+# [multiline-error-info]
+# SyntaxError: [error-reason] ([file-name], line [line-number])
+python() {
+    garbage(code
+}

integration-tests/project-folder/sources/meta-error/recipes-error/error/execution-python-functioni.bb

@@ -0,0 +1,6 @@
+# ERROR: [file-path]: Error executing a python function in  <code>:
+# [multiline-error-info]
+# Exception: TypeError: [error-reason]
+python() {
+    '2' + 2
+}

integration-tests/project-folder/sources/meta-error/recipes-error/error/unable-to-parse.bb

@@ -0,0 +1,7 @@
+# WARNING: [file-path]: Error during finalise of [file-path]
+# ERROR: Unable to parse [file-path]
+# [multiline-error-info]
+# SyntaxError: [error-reason]
+python do_compile() {
+    garbage(code
+}

integration-tests/project-folder/sources/meta-error/recipes-error/error/unparsed-line.bb

@@ -0,0 +1,6 @@
+# NOTE:
+# Some error lines start with 'Parsing recipes...' but sometimes these words appear on a different line than the ones with 'ERROR:'
+# Henc do not use '^Parsing recipes...' as part of the regex
+
+# ERROR: ParseError at [file-path]:[line-number]: unparsed line: 'undefinedvariable'
+undefinedvariable