[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262087#comment-17262087
]
Viraj Jasani edited comment on PHOENIX-6288 at 1/10/21, 5:27 AM:
-----------------------------------------------------------------
At least I think we have the known root cause now. The past 2 builds (for the
first time ever I have seen on master branch) have all tests passed, build
successful for phoenix-core and it failed for phoenix-client and phoenix-server
with
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project
phoenix-server: Error creating shaded jar:
/home/jenkins/jenkins-agent/workspace/enix-PreCommit-GitHub-PR_PR-1080/yetus-general-check/src/phoenix-core/target/classes
(Is a directory) -> [Help 1]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default-shaded) on
project phoenix-client: Error creating shaded jar:
/home/jenkins/jenkins-agent/workspace/enix-PreCommit-GitHub-PR_PR-1080/yetus-general-check/src/phoenix-core/target/classes
(Is a directory) -> [Help 1]
{code}
{code:java}
[INFO] Apache Phoenix ..................................... SUCCESS [ 2.759 s]
[INFO] Phoenix Hbase 2.4.0 compatibility .................. SUCCESS [ 9.346 s]
[INFO] Phoenix Hbase 2.3.0 compatibility .................. SUCCESS [ 2.794 s]
[INFO] Phoenix Hbase 2.2.1 compatibility .................. SUCCESS [ 2.612 s]
[INFO] Phoenix Hbase 2.1.6 compatibility .................. SUCCESS [ 1.479 s]
[INFO] Phoenix Core ....................................... SUCCESS [ 03:33 h]
[INFO] Phoenix - Pherf .................................... SUCCESS [16:22 min]
[INFO] Phoenix Client Parent .............................. SUCCESS [ 3.934 s]
[INFO] Phoenix Client ..................................... FAILURE [ 2.962 s]
[INFO] Phoenix Server ..................................... FAILURE [ 3.262 s]
[INFO] Phoenix - Tracing Web Application .................. SUCCESS [ 23.624 s]
[INFO] Phoenix Assembly ................................... SKIPPED
[INFO] phoenix-tools ...................................... SUCCESS [02:57 min]
{code}
This is same for both of last 2 builds:
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1080/2/artifact/yetus-general-check/output/patch-unit-root.txt]
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1080/3/artifact/yetus-general-check/output/patch-unit-root.txt]
was (Author: vjasani):
At least I think we have the known root cause now. The past 2 builds (for the
first time ever I have seen on master branch) have all tests passed, build
successful for phoenix-core and it failed for phoenix-client and phoenix-server
with
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project
phoenix-server: Error creating shaded jar:
/home/jenkins/jenkins-agent/workspace/enix-PreCommit-GitHub-PR_PR-1080/yetus-general-check/src/phoenix-core/target/classes
(Is a directory) -> [Help 1]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default-shaded) on
project phoenix-client: Error creating shaded jar:
/home/jenkins/jenkins-agent/workspace/enix-PreCommit-GitHub-PR_PR-1080/yetus-general-check/src/phoenix-core/target/classes
(Is a directory) -> [Help 1]
{code}
{code:java}
[INFO] Apache Phoenix ..................................... SUCCESS [ 2.759 s]
[INFO] Phoenix Hbase 2.4.0 compatibility .................. SUCCESS [ 9.346 s]
[INFO] Phoenix Hbase 2.3.0 compatibility .................. SUCCESS [ 2.794 s]
[INFO] Phoenix Hbase 2.2.1 compatibility .................. SUCCESS [ 2.612 s]
[INFO] Phoenix Hbase 2.1.6 compatibility .................. SUCCESS [ 1.479 s]
[INFO] Phoenix Core ....................................... SUCCESS [ 03:33 h]
[INFO] Phoenix - Pherf .................................... SUCCESS [16:22 min]
[INFO] Phoenix Client Parent .............................. SUCCESS [ 3.934 s]
[INFO] Phoenix Client ..................................... FAILURE [ 2.962 s]
[INFO] Phoenix Server ..................................... FAILURE [ 3.262 s]
[INFO] Phoenix - Tracing Web Application .................. SUCCESS [ 23.624 s]
[INFO] Phoenix Assembly ................................... SKIPPED
[INFO] phoenix-tools ...................................... SUCCESS [02:57 min]
{code}
This is same for both of last 2 builds:
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1080/2/artifact/yetus-general-check/output/patch-unit-root.txt
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1080/3/artifact/yetus-general-check/output/patch-unit-root.txt
> Minicluster startup problems on Jenkins
> ---------------------------------------
>
> Key: PHOENIX-6288
> URL: https://issues.apache.org/jira/browse/PHOENIX-6288
> Project: Phoenix
> Issue Type: Bug
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
> Fix For: 5.1.0, 4.16.0
>
>
> We are sporadically getting Test failures on Jenkins that are caused by the
> miniCluster startup timeouts.
> {noformat}
> Caused by: java.lang.RuntimeException: Master not active after 30000ms at
> org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
>
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430)
> at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259)
> ... 43 more
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
