giscanner: give message.ERROR a purpose

It's not yet being used but will be in the future by
annotationparser.py to signal the difference between
message.WARNING:
    something is wrong but the comment block can still
    be parsed and serialized back into a comment block
    without information being lost
message.ERROR:
    something is wrong and the comment block can *not*
    be parsed and serialized back into a comment block
    without information being lost

Different tools can then act accordingly. Nothing will
change for g-ir-scanner but this will be important for
the GTK-Doc comment block rewriting tool to prevent
extremely broken input leading to even more broken
output...

1 files changed, 2 insertions, 2 deletions

diff --git a/tests/warn/warningtester.py b/tests/warn/warningtester.py
index c78f92a7..b2117910 100644
--- a/tests/warn/warningtester.py
+++ b/tests/warn/warningtester.py
@@ -14,7 +14,7 @@ from giscanner.annotationparser import GtkDocCommentBlockParser
 from giscanner.ast import Include, Namespace
 from giscanner.introspectablepass import IntrospectablePass
 from giscanner.maintransformer import MainTransformer
-from giscanner.message import MessageLogger
+from giscanner.message import MessageLogger, WARNING, ERROR, FATAL
 from giscanner.sourcescanner import SourceScanner
 from giscanner.transformer import Transformer
 from giscanner.scannermain import process_packages
@@ -97,7 +97,7 @@ def check(args):
     output = ChunkedIO()
     namespace = Namespace('Test', '1.0')
     logger = MessageLogger.get(namespace=namespace, output=output)
-    logger.enable_warnings(True)
+    logger.enable_warnings((WARNING, ERROR, FATAL))
 
     transformer = Transformer(namespace)
     transformer.set_include_paths([os.path.join(top_srcdir, 'gir'), top_builddir])