[
https://issues.apache.org/jira/browse/IMPALA-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904847#comment-17904847
]
ASF subversion and git services commented on IMPALA-13536:
----------------------------------------------------------
Commit 490f90c65e00510f21c909b367d027d2e3582f04 in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=490f90c65 ]
IMPALA-13536: Fix Workload Management Init Tests Issues
Several problems with the workload management code and
test_workload_mgmt_init.py tests have been uncovered by the Ozone
tests.
* test_create_on_version_1_0_0 - Test comment said it ran on 10
nodes, test configuration specified 1 node. Fix was to modify
the test configuration.
* test_create_on_version_1_1_0 - Test comment said it ran on 10
nodes, test configuration specified 1 node. Fix was to modify
the test configuration.
* test_invalid_* - All four of these tests run the same internal
function to execute the test. This internal function was not
waiting long enough for the expected failure to appear. The
fixed internal function waits longer for the expected failure.
Additionally, the @CustomClusterTestSuite annotation has a new option
named 'log_symlinks', which, if set to True will resolve all daemon
log symlinks and output their actual paths to the log. Failed tests
can then be easily traced to the exact log files for that test.
The existing workload management tests in testdata have been expanded
to also assert the expected table properties are present.
Modified tests passed on Ozone builds both with and without erasure
coding enabled.
Change-Id: Ie3f34088d1d925f30abb63471387e6fdb62b95a7
Reviewed-on: http://gerrit.cloudera.org:8080/22119
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Tests failing in TestWorkloadManagementInitWait on Ozone
> --------------------------------------------------------
>
> Key: IMPALA-13536
> URL: https://issues.apache.org/jira/browse/IMPALA-13536
> Project: IMPALA
> Issue Type: Bug
> Reporter: Daniel Becker
> Assignee: Jason Fehr
> Priority: Blocker
> Labels: broken-build
>
> Some of our tests failed in the test class
> test_workload_mgmt_init.py::TestWorkloadManagementInitWait.
> test_upgrade_1_0_0_to_1_1_0():
> {code:java}
> custom_cluster/test_workload_mgmt_init.py:222: in test_upgrade_1_0_0_to_1_1_0
> self.check_schema_version("1.1.0")
> custom_cluster/test_workload_mgmt_init.py:129: in check_schema_version
> self.assert_table_prop(tbl_name, "wm_schema_version", schema_version)
> custom_cluster/test_workload_mgmt_init.py:104: in assert_table_prop
> assert found, "did not find expected table prop '{}' with value '{}' on
> table " \
> E AssertionError: did not find expected table prop 'wm_schema_version' with
> value '1.1.0' on table 'sys.impala_query_log'
> E assert False
> {code}
> test_invalid_wm_schema_version_live_table_prop():
> {code:java}
> custom_cluster/test_workload_mgmt_init.py:375: in
> test_invalid_wm_schema_version_live_table_prop
> self._run_invalid_table_prop_test(self.QUERY_TBL_LIVE,
> "wm_schema_version")
> custom_cluster/test_workload_mgmt_init.py:325: in _run_invalid_table_prop_test
> "found on the '{}' property of table '{}'".format(prop_name, table))
> common/impala_test_suite.py:1351: in assert_catalogd_log_contains
> daemon, level, line_regex, expected_count, timeout_s, dry_run)
> common/impala_test_suite.py:1397: in assert_log_contains
> (expected_count, log_file_path, line_regex, found, line)
> E AssertionError: Expected 1 lines in file
> /data0/jenkins/workspace/impala-asf-master-core-ozone-erasure-coding/repos/Impala/logs/custom_cluster_tests/catalogd.impala-ec2-centos79-m6i-4xlarge-xldisk-126a.vpc.cloudera.com.jenkins.log.FATAL.20241107-042724.11427
> matching regex 'could not parse version string '' found on the
> 'wm_schema_version' property of table 'sys.impala_query_live'', but found 0
> lines. Last line was:
> E . Impalad exiting.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
