From 76b9791ef73bcaafa9d4912e16d0eb4a8d7ebba4 Mon Sep 17 00:00:00 2001 From: Karel Zak Date: Tue, 14 Nov 2023 09:31:31 +0100 Subject: [PATCH] tests: don't keep bison messages in tests Bison generates the 'syntax error' messages and depends on the Bison version. For example, the current bison uses lsfd: failed to parse "(": syntax error, unexpected end of file But the old version: lsfd: failed to parse "(": syntax error, unexpected $end We do not control these strings, so it's better not to save them to our tests. Signed-off-by: Karel Zak --- tests/expected/lsfd/filter-broken-exp | 6 +++--- tests/ts/lsfd/filter-broken-exp | 3 +++ 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/tests/expected/lsfd/filter-broken-exp b/tests/expected/lsfd/filter-broken-exp index 6ed2bf0ec9..61512e0117 100644 --- a/tests/expected/lsfd/filter-broken-exp +++ b/tests/expected/lsfd/filter-broken-exp @@ -1,4 +1,4 @@ -lsfd: failed to parse "(": syntax error, unexpected end of file -lsfd: failed to parse ")": syntax error, unexpected ')' -lsfd: failed to parse "(FD == 1)garbage": syntax error, unexpected HOLDER, expecting end of file +lsfd: failed to parse "(": +lsfd: failed to parse ")": +lsfd: failed to parse "(FD == 1)garbage": lsfd: unknown column: NOSUCHCOLUMN diff --git a/tests/ts/lsfd/filter-broken-exp b/tests/ts/lsfd/filter-broken-exp index 1cec451cf8..1854e508ea 100755 --- a/tests/ts/lsfd/filter-broken-exp +++ b/tests/ts/lsfd/filter-broken-exp @@ -31,4 +31,7 @@ ts_cd "$TS_OUTDIR" $TS_CMD_LSFD -Q 'NOSUCHCOLUMN' } > $TS_OUTPUT 2>&1 +sed -i -e 's/syntax error.*//g' \ + $TS_OUTPUT $TS_ERRLOG + ts_finalize -- 2.47.3