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

Hadoop QA commented on HDDS-447:
--------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
22s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} ozone-0.2 Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  7m 
44s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m 
24s{color} | {color:green} ozone-0.2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 16m 
35s{color} | {color:green} ozone-0.2 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 14m  
3s{color} | {color:green} ozone-0.2 passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
10m 39s{color} | {color:green} branch has no errors when building and testing 
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  7m 
12s{color} | {color:green} ozone-0.2 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
30s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 28m 
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 15m 
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 15m 
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 13m 
57s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} shellcheck {color} | {color:red}  0m 
25s{color} | {color:red} The patch generated 3 new + 1 unchanged - 0 fixed = 4 
total (was 1) {color} |
| {color:orange}-0{color} | {color:orange} shelldocs {color} | {color:orange}  
0m 14s{color} | {color:orange} The patch generated 6 new + 106 unchanged - 10 
fixed = 112 total (was 116) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git 
apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply 
{color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green}  0m 
15s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
10m 56s{color} | {color:green} patch has no errors when building and testing 
our client artifacts. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red}  7m 
52s{color} | {color:red} root generated 2 new + 4235 unchanged - 0 fixed = 4237 
total (was 4235) {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 15m  3s{color} 
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
48s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}173m  9s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.security.TestRaceWhenRelogin |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:ba1ab08 |
| JIRA Issue | HDDS-447 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12939901/HDDS-447-ozone-0.2.001.patch
 |
| Optional Tests |  asflicense  shellcheck  shelldocs  compile  javac  javadoc  
mvninstall  mvnsite  unit  shadedclient  xml  |
| uname | Linux 1c0e4366ae3a 4.4.0-133-generic #159-Ubuntu SMP Fri Aug 10 
07:31:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | ozone-0.2 / dca8d0c |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_181 |
| shellcheck | v0.4.6 |
| shellcheck | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1096/artifact/out/diff-patch-shellcheck.txt
 |
| shelldocs | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1096/artifact/out/diff-patch-shelldocs.txt
 |
| whitespace | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1096/artifact/out/whitespace-eol.txt
 |
| javadoc | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1096/artifact/out/diff-javadoc-javadoc-root.txt
 |
| unit | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1096/artifact/out/patch-unit-root.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1096/testReport/ |
| Max. process+thread count | 1367 (vs. ulimit of 10000) |
| modules | C: hadoop-project hadoop-dist hadoop-hdds hadoop-hdds/tools 
hadoop-ozone hadoop-ozone/common hadoop-ozone/client hadoop-ozone/tools 
hadoop-ozone/integration-test hadoop-ozone/ozonefs hadoop-ozone/datanode . 
hadoop-ozone/dist U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1096/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> separate ozone-dist and hadoop-dist projects with real classpath separation
> ---------------------------------------------------------------------------
>
>                 Key: HDDS-447
>                 URL: https://issues.apache.org/jira/browse/HDDS-447
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>         Attachments: HDDS-447-ozone-0.2.001.patch
>
>
> Currently we have the same hadoop-dist project to create both the ozone and 
> and the hadoop distribution.
> To decouple ozone and hadoop build it would be great to create two different 
> dist project.
> The hadoop-dist should be cloned to hadoop-ozone/dist and from 
> hadoop-dist/pom.xml we can remove the hdds/ozone related items and from 
> hadoop-ozone/dist/pom.xml we can remove the core hadoop related part.
> An other issue with the current distribution schema is the lack of real 
> classpath separation. 
> The current hadoop distribution model is defined in the hadoop-project-dist 
> which is parent of all the component projects and the output of the 
> distribution generation will be copied by the dist-layout-stitching. There is 
> no easy way to use command specific classpath as the classpath is defined in 
> component level (hdfs/yarn/mapreduce).
> With this approach we will have a lot of unnecessary dependencies on the 
> classpath (which were not on the classpath at the time of the unit tests) and 
> it's not possible (as an example) use different type of jaxrs stack for 
> different services (s3gateway vs scm).
> As a simplified but more effective approach I propose to use the following 
> method:
> 1. don't use hadoop-project-dist for ozone projects any more
> 2. During the build generate a classpath descriptor (with the 
> dependency:build-classpath maven plugin/goal) for all the projects
> 3. During the distribution copy all the required dependencies (with 
> dependency:copy maven plugin/goal) to a lib folder (share/ozone/lib)
> 4. During the distribution copy all the classpath descriptors to the 
> classpath folder (share/ozone/classpath)
> 5. Put only the required jar files to the classpath with reading the 
> classpath descriptor 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to