[ 
https://issues.apache.org/jira/browse/IMPALA-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

gaurav singh updated IMPALA-13315:
----------------------------------
    Summary: Test_tuple_cache_tpc_queries: invalid literal for int() with base 
10: '1a'  (was: CLONE - TestRPCTimeout.test_miss_complete_cb: RPC Failed: Could 
Not Connect)

> Test_tuple_cache_tpc_queries: invalid literal for int() with base 10: '1a'
> --------------------------------------------------------------------------
>
>                 Key: IMPALA-13315
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13315
>             Project: IMPALA
>          Issue Type: Bug
>    Affects Versions: Impala 4.5.0
>            Reporter: gaurav singh
>            Priority: Minor
>              Labels: broken-build, flaky-test
>             Fix For: Impala 4.5.0
>
>
> Custom cluster test assert failure:
> Error:
> {noformat}
> assert 'Query aborted' in 'Query dc4af3c7143ae570:142a80e300000000 
> failed:\nExec() rpc failed: Remote error: Runtime error: Debug Action: 
> IMPALA_SERVICE_POOL:FAIL\n\n'  +  where 'Query 
> dc4af3c7143ae570:142a80e300000000 failed:\nExec() rpc failed: Remote error: 
> Runtime error: Debug Action: IMPALA_SERVICE_POOL:FAIL\n\n' = 
> str(ImpalaBeeswaxException())
> {noformat}
> Stack Trace:
> {noformat}
> custom_cluster/test_rpc_timeout.py:231: in test_miss_complete_cb
>     assert "Query aborted" in str(ex)
> E   assert 'Query aborted' in 'Query dc4af3c7143ae570:142a80e300000000 
> failed:\nExec() rpc failed: Remote error: Runtime error: Debug Action: 
> IMPALA_SERVICE_POOL:FAIL\n\n'
> E    +  where 'Query dc4af3c7143ae570:142a80e300000000 failed:\nExec() rpc 
> failed: Remote error: Runtime error: Debug Action: 
> IMPALA_SERVICE_POOL:FAIL\n\n' = str(ImpalaBeeswaxException())
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to