[ 
https://issues.apache.org/jira/browse/PHOENIX-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268529#comment-17268529
 ] 

Viraj Jasani edited comment on PHOENIX-6327 at 1/20/21, 11:45 AM:
------------------------------------------------------------------

Recent 4.x multibranch build is also aborted 
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/208/] 

For master, 2.1 build seems aborted 
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/205/]

Seems like these timeouts are related to something else.

It could be env issues too, this is what I found with 2.2 profile build:
{code:java}
16:52:13  H6 was marked offline: This agent is offline because Jenkins failed 
to launch the agent process on it.
Error when executing always post condition:
java.io.IOException: Unable to create live FilePath for H6
        at 
org.jenkinsci.plugins.workflow.support.steps.FilePathDynamicContext.get(FilePathDynamicContext.java:64)

{code}


was (Author: vjasani):
Recent 4.x multibranch build is also aborted 
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/208/] 

For master, 2.1 build seems aborted 
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/205/]

Seems like these timeouts are related to something else.

> Consolidate Junit test categories
> ---------------------------------
>
>                 Key: PHOENIX-6327
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6327
>             Project: Phoenix
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 5.0.0, 4.15.0
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Minor
>             Fix For: 5.1.0, 4.16.1
>
>
> Phoenix has an HBaseManagedTimeTest category.
> However, there are only two pherf tests in this category, and I see no reason 
> for thoseto have their own category.
> This looks like a leftover from some very old test setup.
> SplitSystemCatalogTests category works the same as the 
> NeedTheirOwnClusterTests.
> Having separate categories hurts execution parallellism and increases test 
> execution time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to