[
https://issues.apache.org/jira/browse/IMPALA-14919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith resolved IMPALA-14919.
------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> TestSelfRenameEvent.test_self_rename_events is flaky
> ----------------------------------------------------
>
> Key: IMPALA-14919
> URL: https://issues.apache.org/jira/browse/IMPALA-14919
> Project: IMPALA
> Issue Type: Bug
> Components: Test
> Reporter: Quanlong Huang
> Assignee: Quanlong Huang
> Priority: Major
> Labels: broken-build
> Fix For: Impala 5.0.0
>
>
> Saw this failure in a downstream build
> {noformat}
> metadata.test_event_processing.TestSelfRenameEvent.test_self_rename_events
> (from pytest){noformat}
> h3. Stacktrace
> {noformat}
> /data/jenkins/workspace/impala-cdw-master-core-s3-arm-data-cache/repos/Impala/tests/metadata/test_event_processing.py:806:
> in test_self_rename_events
> assert events_skipped_after == events_skipped_before + 2
> E assert 30 == 31
> E +30
> E -31
> alter_client = <tests.common.impala_connection.ImpylaHS2Connection
> object at 0xffff9850ed30>
> alter_handle = <tests.common.impala_connection.OperationHandle object
> at 0xffff956ffdc0>
> catalogd = <CatalogdProcess PID: 84432
> (/data/jenkins/workspace/impala-cdw-master-core-s3-arm-data-cache/repos/Impala/be/build/la...sts
> -kudu_master_hosts 127.0.0.1 -catalog_service_port=26000
> -state_store_subscriber_port=23020 -webserver_port=25020)>
> events_skipped_after = 30
> events_skipped_before = 29
> self =
> <tests.metadata.test_event_processing.TestSelfRenameEvent object at
> 0xffff956ffcd0>
> start_time = 1776887185.0192785
> unique_database = 'test_self_rename_events_43dbc286'
> version_after_create = 2154{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)