[IMPALA-7192] test_timestamp_out_of_range doesn't fail on invalid timestamp

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: Impala 3.1.0
• Component/s: Backend
• Labels: broken-build
• Epic Color: ghx-label-3
• Assignee: Unassigned
• Reporter: Tianyi Wang
• Created: 21/Jun/18 00:10
• Updated: 18/Sep/18 03:55
• Resolved: 18/Sep/18 03:55

Description

It's an ASAN build

07:29:23  TestParquet.test_timestamp_out_of_range[exec_option: {'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0, 'disable_codegen': True, 'abort_on_error': 1, 'debug_action': '-1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0', 'exec_single_node_rows_threshold': 0} | table_format: parquet/none] 
07:29:23 [gw6] linux2 -- Python 2.7.5 /data/jenkins/workspace/impala-asf-master-core-asan/repos/Impala/bin/../infra/python/env/bin/python
07:29:23 query_test/test_scanners.py:316: in test_timestamp_out_of_range
07:29:23     vector, unique_database)
07:29:23 common/impala_test_suite.py:420: in run_test_case
07:29:23     assert False, "Expected exception: %s" % expected_str
07:29:23 E   AssertionError: Expected exception: Parquet file 'hdfs://localhost:20500/test-warehouse/$DATABASE.db/out_of_range_timestamp/out_of_range_timestamp.parquet' column 'ts' contains an out of range timestamp. The valid date range is 1400-01-01..9999-12-31.

Issue Links

• duplicates: IMPALA-7335 Assertion Failure - test_corrupt_files