[
https://issues.apache.org/jira/browse/HBASE-20162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393977#comment-16393977
]
Hudson commented on HBASE-20162:
--------------------------------
Results for branch branch-1.2
[build #262 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/262/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/262//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/262//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/262//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [nightly] depending on pipeline execution we sometimes refer to the wrong
> workspace
> -----------------------------------------------------------------------------------
>
> Key: HBASE-20162
> URL: https://issues.apache.org/jira/browse/HBASE-20162
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.0, 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 1.4.3
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 2.0.0, 3.0.0, 2.1.0, 1.5.0, 1.3.3, 1.2.8, 1.4.3
>
> Attachments: HBASE-20162.0.patch
>
>
> we set BASEDIR at the top of our pipeline to point at the component checkout
> within WORKSPACE.
> but!
> a) at that point WORKSPACE is the workspace for the launching task
> b) sometimes our parallel executions get a task with a different local
> WORKSPACE to allow for coexisting on the same build host
> c) when this happens our parallel stages are referring to some other absolute
> path on the host
> d) in most cases we're referring to dev-support files like e.g. the nightly
> build script or machine info script that are the same across branches so
> things are fine if we aren't running at the same time as a job that's
> overwritting them
> e) we also refer to the Dockerfile this way, so weird bugs I'm sure.
> f) we build the source tarball from here, so that's probably broken subtly
> g) sometimes that other directory _doesn't exist at all_ and we fail with
> confusing messages about stuff not found
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
