[
https://issues.apache.org/jira/browse/IMPALA-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089558#comment-18089558
]
Joe McDonnell commented on IMPALA-13862:
----------------------------------------
The zdump utility gives details. On Ubuntu, the oldest entries for "zdump -v
CET" are:
{noformat}
$ zdump -v CET
CET -9223372036854775808 = NULL
CET -9223372036854689408 = NULL
CET Sun Apr 30 21:59:59 1916 UT = Sun Apr 30 22:59:59 1916 CET isdst=0
gmtoff=3600
CET Sun Apr 30 22:00:00 1916 UT = Mon May 1 00:00:00 1916 CEST isdst=1
gmtoff=7200
CET Sat Sep 30 22:59:59 1916 UT = Sun Oct 1 00:59:59 1916 CEST isdst=1
gmtoff=7200
CET Sat Sep 30 23:00:00 1916 UT = Sun Oct 1 00:00:00 1916 CET isdst=0
gmtoff=3600
{noformat}
For Redhat 10, it looks like this:
{noformat}
# zdump -v CET
CET -9223372036854775808 = NULL
CET -9223372036854689408 = NULL
CET Wed Dec 31 23:42:29 1879 UT = Wed Dec 31 23:59:59 1879 LMT isdst=0
gmtoff=1050
CET Wed Dec 31 23:42:30 1879 UT = Thu Jan 1 00:00:00 1880 BMT isdst=0
gmtoff=1050
CET Sat Apr 30 23:59:59 1892 UT = Sun May 1 00:17:29 1892 BMT isdst=0
gmtoff=1050
CET Sun May 1 00:00:00 1892 UT = Sun May 1 00:00:00 1892 WET isdst=0 gmtoff=0
CET Sat Nov 7 23:59:59 1914 UT = Sat Nov 7 23:59:59 1914 WET isdst=0 gmtoff=0
CET Sun Nov 8 00:00:00 1914 UT = Sun Nov 8 01:00:00 1914 CET isdst=0
gmtoff=3600
CET Sun Apr 30 22:59:59 1916 UT = Sun Apr 30 23:59:59 1916 CET isdst=0
gmtoff=3600
CET Sun Apr 30 23:00:00 1916 UT = Mon May 1 01:00:00 1916 CEST isdst=1
gmtoff=7200
{noformat}
On Redhat, it may be tied to the version of the tzdata package. When I run
Rocky 9.3, it has the first (tzdata is 2023c-1.el9). When I install the latest
tzdata (2026b-1.el9_8), it has the second. It may have come in around 2024b:
[https://lists.iana.org/hyperkitty/list/[email protected]/thread/IZ7AO6WRE3W3TWBL5IR6PMQUL433BQIE/]
Not sure why Ubuntu is different.
> test_int64_timestamps fails in Dockerised tests running on Rocky 8.5
> --------------------------------------------------------------------
>
> Key: IMPALA-13862
> URL: https://issues.apache.org/jira/browse/IMPALA-13862
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 5.0.0
> Reporter: Laszlo Gaal
> Priority: Major
> Labels: regression
>
> When dockerised EE_TESTs are executed on Rocky 8.5, test_int64_timestamp
> exhibits a single failed test. It is repeated 8 times as the test is run
> through different test vectors, but all 8 failures are actually the same
> item. The stack trace:
> {code}
> query_test/test_scanners.py:1172: in test_int64_timestamps
> 'QueryTest/parquet-int64-timestamps', vector, unique_database)
> common/impala_test_suite.py:904: in run_test_case
> self.__verify_results_and_errors(vector, test_section, result, use_db)
> common/impala_test_suite.py:737: in __verify_results_and_errors
> replace_filenames_with_placeholder)
> common/test_result_verifier.py:523: in verify_raw_results
> VERIFIER_MAP[verifier](expected, actual)
> common/test_result_verifier.py:305: in verify_query_result_is_equal
> assert expected_results == actual_results
> E assert Comparing QueryTestResults (expected vs actual):
> E -2147483648,1970-01-01 00:59:57.852516352,1969-12-31 23:59:57.852516352
> == -2147483648,1970-01-01 00:59:57.852516352,1969-12-31 23:59:57.852516352
> E -9223372036854775808,1677-09-21 01:12:43.145224192,1677-09-21
> 00:12:43.145224192 != -9223372036854775808,1677-09-21
> 00:30:13.145224192,1677-09-21 00:12:43.145224192
> E 0,1970-01-01 01:00:00,1970-01-01 00:00:00 == 0,1970-01-01
> 01:00:00,1970-01-01 00:00:00
> E 2147483647,1970-01-01 01:00:02.147483647,1970-01-01 00:00:02.147483647
> == 2147483647,1970-01-01 01:00:02.147483647,1970-01-01 00:00:02.147483647
> E 9223372036854775807,2262-04-12 01:47:16.854775807,2262-04-11
> 23:47:16.854775807 == 9223372036854775807,2262-04-12
> 01:47:16.854775807,2262-04-11 23:47:16.854775807
> E Detailed information truncated (-4 more lines), use "-vv" to show{code}
> (The blank lines around the failing comparison were added for clarity, they
> were not part of the test output.)
> This is seen on the master branch.
> The failure looks OS-specific, or specific to Red Hat derivatives: dockerised
> tests on Ubuntu 20.04 are parts of our precommit process and they have not
> exhibited this failure. The symptoms were first seen during development for
> IMPALA-13825 on Rocky 9.2, then reproduced on private infrastructure on Red
> Hat 9.2; this led to the repro scenario on Rocky 8.5.
> The only successful run retained on jenkins.impala.io for this configuration
> is from August 2023, using commit
> {{75bf21341800aaef87b0fb85af09417fd0a34820}}
> Dockerised tests run the minicluster just like in regular builds (processes
> running natively on the host), but all the Impala roles are run in individual
> Docker containers. The container build logic is located in
> ${IMPALA_HOME}/docker.
> The base OS image for these containers is chosen dynamically to match the
> host's OS, so that impalad binaries can operate both inside and outside the
> containers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
