ayushtkn commented on PR #4415:
URL: https://github.com/apache/hadoop/pull/4415#issuecomment-1206059801

   I tried with -T1C, and first it failed with:
   ```
   [ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:1.11.2:yarn (yarn install) on project 
hadoop-yarn-applications-catalog-webapp: Failed to run task: 'yarn ' failed. 
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit 
value: 1) -> [Help 1]
   [ERROR] 
   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
   [ERROR] 
   [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
   [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
   [ERROR] 
   [ERROR] After correcting the problems, you can resume the build with the 
command
   [ERROR]   mvn <args> -rf :hadoop-yarn-applications-catalog-webapp
   ```
   
   This is yarn stuff and when I do a normal build it passes.
   
   Second time it got hung here:
   ```
   [INFO] --- maven-antrun-plugin:1.7:run (     [mkdir] Create c    [mkdir] 
Created dir: 
/Users/ayushsaxena/code/hadoop-os/hadoop-mapreduce-prreate-testdirs) @ 
hadoop-yarn-server-timelineservice-hbase-client -- 
   ```
   Third time it passed
   
   The behaviour is quite random, it never failed at Mapreduce though, but I 
don't think with such kind of behaviour, we can integrate this with our 
Pre-Commits. We can't trade off time save with random build failures. :-( 


-- 
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]


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

Reply via email to