stack commented on HBASE-20031:

Was thinking on this one afterward.

 # There should be no timeout on ITs because the cluster chassis can be changed 
under them; can be mini cluster or real cluster; can run in small or over the 
 # Did ITs have a classrule before this? Maybe it was added only by the mass 
edit that introduced HCTR? If so, could consider backing out HCTR for ITs -- 
though counter argument might be that HCTR is supposed to be more generic than 
just timeout checking... eventually. [~mdrob] reminder that it different 
phase/plugin argues for purge?

> Unable to run integration test using mvn due to missing HBaseClassTestRule
> --------------------------------------------------------------------------
>                 Key: HBASE-20031
>                 URL: https://issues.apache.org/jira/browse/HBASE-20031
>             Project: HBase
>          Issue Type: Test
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>         Attachments: 20031.v1.txt, 20031.v2.txt, 20031.v3.txt
> In branch-1, the following command works:
> {code}
> mvn test -Dtest=org.apache.hadoop.hbase.IntegrationTestIngest
> {code}
> For hbase2, we have the following error:
> {code}
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.249 
> s <<< FAILURE! - in org.apache.hadoop.hbase.IntegrationTestIngest
> [ERROR] org.apache.hadoop.hbase.IntegrationTestIngest  Time elapsed: 0.01 s  
> <<< FAILURE!
> java.lang.AssertionError: No HBaseClassTestRule ClassRule for 
> org.apache.hadoop.hbase.IntegrationTestIngest
> {code}

This message was sent by Atlassian JIRA

Reply via email to