Build failed in Jenkins: Tez-Build #1417

2016-03-30 Thread Apache Jenkins Server 
See 

Changes:

[hitesh] TEZ-3173. Update Tez AM REST APIs for more information for each vertex.

--
[...truncated 4897 lines...]
[INFO] Working directory: 

[INFO] Storing buildNumber: e416991192d43ea750c3fa78c5cced0e9e6cadc1 at 
timestamp: 1459387060439
[INFO] Executing: /bin/sh -c cd 
 && git rev-parse 
--verify HEAD
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- build-helper-maven-plugin:1.8:maven-version (maven-version) @ 
hadoop-shim-impls ---
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ hadoop-shim-impls ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] 
[INFO] 
[INFO] Building hadoop-shim-2.6 0.8.3-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ hadoop-shim-2.6 ---
[INFO] Deleting 

[INFO] 
[INFO] --- buildnumber-maven-plugin:1.1:create (default) @ hadoop-shim-2.6 ---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd 
 
&& git rev-parse --verify HEAD
[INFO] Working directory: 

[INFO] Storing buildNumber: e416991192d43ea750c3fa78c5cced0e9e6cadc1 at 
timestamp: 1459387060545
[INFO] Executing: /bin/sh -c cd 
 
&& git rev-parse --verify HEAD
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- build-helper-maven-plugin:1.8:maven-version (maven-version) @ 
hadoop-shim-2.6 ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
hadoop-shim-2.6 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
hadoop-shim-2.6 ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
hadoop-shim-2.6 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
hadoop-shim-2.6 ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.14.1:test (default-test) @ hadoop-shim-2.6 
---
[INFO] Surefire report directory: 


---
 T E S T S
---

---
 T E S T S
---
Running org.apache.tez.hadoop.shim.TestHadoop25_26_27ShimProvider
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.201 sec

Results :

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] --- buildnumber-maven-plugin:1.1:create (default) @ hadoop-shim-2.6 ---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd 
 
&& git rev-parse --verify HEAD
[INFO] Working directory: 

[INFO] Storing buildNumber: e416991192d43ea750c3fa78c5cced0e9e6cadc1 at 
timestamp: 1459387061181
[INFO] Executing: /bin/sh -c cd 
 
&& git rev-parse --verify HEAD
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- build-helper-maven-plugin:1.8:maven-version (maven-version) @ 
hadoop-shim-2.6 ---
[INFO] 
[INFO] ---

Jenkins build is back to normal : Tez-Build #1416

2016-03-30 Thread Apache Jenkins Server 
See

[jira] [Created] (TEZ-3191) NM container diagnostics for excess resource usage can be lost if task fails while being killed

2016-03-30 Thread Jason Lowe (JIRA) 
Jason Lowe created TEZ-3191:
---

 Summary: NM container diagnostics for excess resource usage can be 
lost if task fails while being killed
 Key: TEZ-3191
 URL: https://issues.apache.org/jira/browse/TEZ-3191
 Project: Apache Tez
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Jason Lowe


This is the Tez version of MAPREDUCE-4955.  I saw a misconfigured Tez job 
report a task attempt as failed due to a filesystem closed error because the NM 
killed the container due to excess memory usage.  Unfortunately the SIGTERM 
sent by the NM caused the filesystem shutdown hook to close the filesystems, 
and that triggered a failure in the main thread.  If the failure is reported to 
the AM via the umbilical before the NM container status is received via the RM 
then the useful container diagnostics from the NM are lost in the job history.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TEZ-3190) Tez UI 2: Display FATAL/NON-FATAL task failures

2016-03-30 Thread Sreenath Somarajapuram (JIRA) 
Sreenath Somarajapuram created TEZ-3190:
---

 Summary: Tez UI 2: Display FATAL/NON-FATAL task failures
 Key: TEZ-3190
 URL: https://issues.apache.org/jira/browse/TEZ-3190
 Project: Apache Tez
  Issue Type: Sub-task
Reporter: Sreenath Somarajapuram


Once TEZ-3161 is in, tasks will be able to convey the severity of failure using 
any of the TaskFailureType.
This ticket is to display the severity info in the UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)