You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/05/02 00:58:00 UTC
[jira] [Commented] (IMPALA-13466) TestHS2.test_long_polling_success failed as query took longer than expected
[ https://issues.apache.org/jira/browse/IMPALA-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077750#comment-18077750 ]
ASF subversion and git services commented on IMPALA-13466:
----------------------------------------------------------
Commit 89b3307e377351e6920929dec75ee08bfc9f5f4a in impala's branch refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=89b3307e3 ]
IMPALA-13466/IMPALA-14935: Fix flakiness in TestHS2 long polling tests
TestHS2 has a couple tests that verify the timing of
operations with long polling. Specifically, both
test_long_polling_success and test_long_polling_failure
expect the call to take less than a second when using
a long_polling_time_ms of 10000. We've seen flakiness
for both of these test cases, so this loosens the bound
to 4 seconds. This is still enough to verify that long
polling is functioning.
Testing:
- Ran locally for 1000 iterations
Change-Id: I401e972bf9dd71dd0c8c11f9dbf575d3ed09b245
Reviewed-on: http://gerrit.cloudera.org:8080/24225
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> TestHS2.test_long_polling_success failed as query took longer than expected
> ---------------------------------------------------------------------------
>
> Key: IMPALA-13466
> URL: https://issues.apache.org/jira/browse/IMPALA-13466
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.5.0
> Reporter: Andrew Sherman
> Assignee: Joe McDonnell
> Priority: Critical
>
> h3. Error Message
> {code}
> hs2/hs2_test_suite.py:66: in add_session lambda: fn(self)) hs2/hs2_test_suite.py:47: in add_session_helper fn() hs2/hs2_test_suite.py:66: in <lambda> lambda: fn(self)) /data/jenkins/workspace/impala-cdw-master-staging-core-ozone/repos/Impala/tests/hs2/test_hs2.py:392: in test_long_polling_success assert time_diff < 1 E assert 2.419112205505371 < 1
> {code}
> h3. Stacktrace
> {code}
> hs2/hs2_test_suite.py:66: in add_session lambda: fn(self)) hs2/hs2_test_suite.py:47: in add_session_helper fn() hs2/hs2_test_suite.py:66: in <lambda> lambda: fn(self)) /data/jenkins/workspace/impala-cdw-master-staging-core-ozone/repos/Impala/tests/hs2/test_hs2.py:392: in test_long_polling_success assert time_diff < 1 E assert 2.419112205505371 < 1
> {code}
> h3. Standard Error
> {code}
> -- 2024-10-17 13:58:05,065 INFO MainThread: Could not connect to ('::1', 21050, 0, 0) Traceback (most recent call last): File "/data/jenkins/workspace/impala-cdw-master-staging-core-ozone/repos/Impala/infra/python/env-gcc10.4.0/lib/python2.7/site-packages/thrift/transport/TSocket.py", line 137, in open handle.connect(sockaddr) File "/data/jenkins/workspace/impala-cdw-master-staging-core-ozone/Impala-Toolchain/toolchain-packages-gcc10.4.0/python-2.7.16/lib/python2.7/socket.py", line 228, in meth return getattr(self._sock,name)(*args) error: [Errno 111] Connection refused
> {code}
> First time this has failed ever, giving to you [~joemcdonnell] in case it ever happens again
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org