From fcbbe282c1bc80d45318b61fe3f2b5b5209a4bf5 Mon Sep 17 00:00:00 2001
From: Adam Williamson <awilliam@redhat.com>
Date: Tue, 12 Jul 2022 12:25:04 -0700
Subject: [PATCH 5/5] Change syntax_error test for consistent output

Python 3.11 changes the string representation of the
SyntaxError triggered by this test - it now says "expected '('"
instead of just "invalid syntax". This changes the test to use
a different error (incomplete `for` loop) which still has just
"invalid syntax" as its description in Python 3.11. This is the
same 'bad code' used in the similar `test_stdin_syntaxerror` in
the unit tests.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
---
 tests/functional/s/syntax/syntax_error.py  | 2 +-
 tests/functional/s/syntax/syntax_error.txt | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/functional/s/syntax/syntax_error.py b/tests/functional/s/syntax/syntax_error.py
index c93df6b05..a52040112 100644
--- a/tests/functional/s/syntax/syntax_error.py
+++ b/tests/functional/s/syntax/syntax_error.py
@@ -1 +1 @@
-def toto # [syntax-error]
+for # [syntax-error]
diff --git a/tests/functional/s/syntax/syntax_error.txt b/tests/functional/s/syntax/syntax_error.txt
index 2dafd9eb3..78a055cf6 100644
--- a/tests/functional/s/syntax/syntax_error.txt
+++ b/tests/functional/s/syntax/syntax_error.txt
@@ -1 +1 @@
-syntax-error:1:10:None:None::invalid syntax (<unknown>, line 1):UNDEFINED
+syntax-error:1:5:None:None::invalid syntax (<unknown>, line 1):UNDEFINED
-- 
2.37.0