IMPALA-12914: TestBannedLogMessages no longer requires running cluster

Updates test_banned_log_messages.py to no longer require a running
cluster, as it only checks files on disk. This fixes running custom
cluster tests that end with shutting down the cluster via
run-all-tests.sh.

Tested locally with

  FE_TEST=false BE_TEST=false EE_TEST=false JDBC_TEST=false\
JS_TEST=false CLUSTER_TEST_FILES=custom_cluster/test_coordinators.py\
::TestCoordinators::test_exclusive_coordinator_plan run-all-tests.sh

Change-Id: Icfa7d5925bf724d714eaa7fa606defae0822cf93
Reviewed-on: http://gerrit.cloudera.org:8080/21152
Reviewed-by: Riza Suminto <riza.suminto@cloudera.com>
Tested-by: Michael Smith <michael.smith@cloudera.com>
This commit is contained in:
Michael Smith
2024-03-15 13:59:53 -07:00
parent 4477398ae4
commit caf136fae4

View File

@@ -21,10 +21,8 @@ from __future__ import absolute_import, division, print_function
import os
import subprocess
from tests.common.impala_test_suite import ImpalaTestSuite
class TestBannedLogMessages(ImpalaTestSuite):
class TestBannedLogMessages:
"""Verify that specific log messages are banned from Impala logs.
This test suite should be run after all the tests have been run.