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

Lars Volker resolved IMPALA-6399.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.12.0

IMPALA-6399: Increase timeout in test_observability to reduce flakiness

Change-Id: I58f7e7b367e73675be42e85f55fd7698d51f92af
Reviewed-on: http://gerrit.cloudera.org:8080/9034
Reviewed-by: Sailesh Mukil <sail...@cloudera.com>
Tested-by: Lars Volker <l...@cloudera.com>

> test_query_profile_thrift_timestamps failure on exhaustive runs
> ---------------------------------------------------------------
>
>                 Key: IMPALA-6399
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6399
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 2.11.0
>            Reporter: Sailesh Mukil
>            Assignee: Lars Volker
>            Priority: Blocker
>              Labels: broken-build
>             Fix For: Impala 2.12.0
>
>
> test_query_profile_thrift_timestamps seems to have started failing due to the 
> debug profile not becoming available in the expected time limit (60 seconds). 
> This started happening around the time the Meltdown bug patches were applied 
> by AWS, so it could possibly be related.
>  
> A fix could be to just increase the expected time limit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to