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 "Csaba Ringhofer (Jira)" <ji...@apache.org> on 2020/03/31 15:57:00 UTC
[jira] [Updated] (IMPALA-9584) test_analytic_fns is flaky (small
fractional differences in AVG)
[ https://issues.apache.org/jira/browse/IMPALA-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Csaba Ringhofer updated IMPALA-9584:
------------------------------------
Description:
The issue occurred here:
https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/2065/testReport/query_test.test_queries/TestQueries/test_analytic_fns_protocol__hs2___exec_option____batch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0____table_format__parquet_none_/
The same test failed with all protocols.
Failing query:
https://github.com/apache/impala/blob/ebbe52b4bed944d3012e3679dc984827ce11d5a8/testdata/workloads/functional-query/queries/QueryTest/analytic-fns.test#L2
Errors are like (hs2):
2009,3,6,3.666666666666667,2009-03-01 20:12:00.475000,'0','8' != 2009,3,6,3.66666666667,2009-03-01 20:12:00.474999,'0','8'
I think that the problem is not the difference in the 4th double column, as that depends on the client used and we do not require complete match during comparison. So the problem is likely to be the timestamp in the 5th column.
was:
The issue occurred here:
https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/2065/testReport/query_test.test_queries/TestQueries/test_analytic_fns_protocol__hs2___exec_option____batch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0____table_format__parquet_none_/
Failing query:
https://github.com/apache/impala/blob/ebbe52b4bed944d3012e3679dc984827ce11d5a8/testdata/workloads/functional-query/queries/QueryTest/analytic-fns.test#L2
Errors are like:
2009,3,6,3.666666666666667,2009-03-01 20:12:00.475000,'0','8' != 2009,3,6,3.66666666667,2009-03-01 20:12:00.474999,'0','8'
> test_analytic_fns is flaky (small fractional differences in AVG)
> ----------------------------------------------------------------
>
> Key: IMPALA-9584
> URL: https://issues.apache.org/jira/browse/IMPALA-9584
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Csaba Ringhofer
> Priority: Major
> Labels: flaky-test
>
> The issue occurred here:
> https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/2065/testReport/query_test.test_queries/TestQueries/test_analytic_fns_protocol__hs2___exec_option____batch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0____table_format__parquet_none_/
> The same test failed with all protocols.
> Failing query:
> https://github.com/apache/impala/blob/ebbe52b4bed944d3012e3679dc984827ce11d5a8/testdata/workloads/functional-query/queries/QueryTest/analytic-fns.test#L2
> Errors are like (hs2):
> 2009,3,6,3.666666666666667,2009-03-01 20:12:00.475000,'0','8' != 2009,3,6,3.66666666667,2009-03-01 20:12:00.474999,'0','8'
> I think that the problem is not the difference in the 4th double column, as that depends on the client used and we do not require complete match during comparison. So the problem is likely to be the timestamp in the 5th column.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org