abstractdog commented on PR #441:
URL: https://github.com/apache/tez/pull/441#issuecomment-3785514101

   > > I'm speculating and might be wrong but is it possible that the 
`-Dmaven.repo.local=/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-441/yetus-m2/tez-master-patch-0`
 is gone by the time this ran?
   > > ```
   > > /patch-mvninstall-tez-tests.txt
   > > /patch-mvninstall-tez-tools_tez-javadoc-tools.txt
   > > ```
   > > 
   > > 
   > >     
   > >       
   > >     
   > > 
   > >       
   > >     
   > > 
   > >     
   > >   
   > > ```
   > > WARNING] The POM for org.apache.tez:tez-api:jar:1.0.0-SNAPSHOT is 
invalid, transitive dependencies (if any) will not be available, enable debug 
logging for more details
   > > [WARNING] The POM for 
org.apache.tez:tez-runtime-library:jar:1.0.0-SNAPSHOT is invalid, transitive 
dependencies (if any) will not be available, enable debug logging for more 
details
   > > [WARNING] The POM for org.apache.tez:tez-mapreduce:jar:1.0.0-SNAPSHOT is 
invalid, transitive dependencies (if any) will not be available, enable debug 
logging for more details
   > > [WARNING] The POM for org.apache.tez:tez-dag:jar:1.0.0-SNAPSHOT is 
invalid, transitive dependencies (if any) will not be available, enable debug 
logging for more details
   > > ```
   > 
   > As its not able to find the previously build modules
   
   but right before these modules' build, there is e.g. tez-dag build as shown 
in
   
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-441/3/artifact/out/patch-mvninstall-tez-dag.txt
   
   which ends with:
   ```
   [INFO] Installing 
/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-441/src/tez-dag/target/tez-dag-1.0.0-SNAPSHOT.jar
 to 
/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-441/yetus-m2/tez-master-patch-0/org/apache/tez/tez-dag/1.0.0-SNAPSHOT/tez-dag-1.0.0-SNAPSHOT.jar
   ```
   I cannot reproduce this locally now, and now it's not only tez-javadoc-tools 
but also tez-tests
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to