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

Michael Wu updated EAGLE-376:
-----------------------------
    Description: 
Add the reason for doing this: 

There we found some Unit Test cases for testing against embedded hbase, which 
usually failed due to the unstable performance of embedded hbase (setup for 
some unit test). They often made CI jobs timeout and as a result, compromised 
the exposure of true problems of other components test cases. For the testing 
target of these faulty cases have been tested well for a long time, we decide 
to just ignore them and give the CI jobs chances to expose TRUE failures if 
there is any.

  was:There we found some Unit Test cases for testing against embedded hbase, 
which usually failed due to the unstable performance of embedded hbase (setup 
for some unit test). They often made CI jobs timeout and as a result, 
compromised the exposure of true problems of other components test cases. For 
the testing target of these faulty cases have been tested well for a long time, 
we decide to just ignore them and give the CI jobs chances to expose TRUE 
failures if there is any.


> skip faulty hbase related UT code
> ---------------------------------
>
>                 Key: EAGLE-376
>                 URL: https://issues.apache.org/jira/browse/EAGLE-376
>             Project: Eagle
>          Issue Type: Task
>            Reporter: Michael Wu
>            Assignee: Michael Wu
>
> Add the reason for doing this: 
> There we found some Unit Test cases for testing against embedded hbase, which 
> usually failed due to the unstable performance of embedded hbase (setup for 
> some unit test). They often made CI jobs timeout and as a result, compromised 
> the exposure of true problems of other components test cases. For the testing 
> target of these faulty cases have been tested well for a long time, we decide 
> to just ignore them and give the CI jobs chances to expose TRUE failures if 
> there is any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to