[
https://issues.apache.org/jira/browse/HBASE-20162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392293#comment-16392293
]
Hadoop QA commented on HBASE-20162:
-----------------------------------
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
28s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
8s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
0s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
18s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 1m 3s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20162 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12913695/HBASE-20162.0.patch |
| Optional Tests | asflicense shellcheck shelldocs |
| uname | Linux e4966669fbc6 3.13.0-137-generic #186-Ubuntu SMP Mon Dec 4
19:09:19 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 4e821d4916 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| shellcheck | v0.4.4 |
| Max. process+thread count | 43 (vs. ulimit of 10000) |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/11877/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> [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
> 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)
