[
https://issues.apache.org/jira/browse/HBASE-14760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989990#comment-14989990
]
Sean Busbey commented on HBASE-14760:
-------------------------------------
hbase-procedure has the same thing. should probably make sure it's not in any
modules.
{code}
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<!-- Always skip the second part executions, since we only run
simple unit tests in this module. -->
<executions>
<execution>
<id>secondPartTestsExecution</id>
<phase>test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<skip>true</skip>
</configuration>
</execution>
</executions>
</plugin>
{code}
> Category-based timeout on TestAsyncProcess makes it so the test is not
> running as part of general build
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-14760
> URL: https://issues.apache.org/jira/browse/HBASE-14760
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
>
> Over in
> https://issues.apache.org/jira/browse/HBASE-14758?focusedCommentId=14989134&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14989134
> , [~carp84] found that since HBASE-14725, the likes of TestAsyncProcess no
> longer runs as part of general build.
> It seems like any test that gets a category-based timer in that patch no
> longer runs as part of the build.
> The test runs fine if I invoke on cmd-line.
> Other category-based timeout tests seem to show in the general build.
> Looking....
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
