-
Type:
Bug
-
Status: Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.8.0, 3.0.0-alpha1
-
Component/s: test
-
Labels:None
-
Target Version/s:
-
Hadoop Flags:Reviewed
From https://builds.apache.org/job/PreCommit-YARN-Build/9976/artifact/patchprocess/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-jobclient-jdk1.8.0_66.txt TestNetworkedJob are failed intermittently.
Running org.apache.hadoop.mapred.TestNetworkedJob Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 81.131 sec <<< FAILURE! - in org.apache.hadoop.mapred.TestNetworkedJob testNetworkedJob(org.apache.hadoop.mapred.TestNetworkedJob) Time elapsed: 30.55 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[[Tue Dec 15 14:02:45 +0000 2015] Application is Activated, waiting for resources to be assigned for AM. Details : AM Partition = <DEFAULT_PARTITION> ; Partition Resource = <memory:8192, vCores:16> ; Queue's Absolute capacity = 100.0 % ; Queue's Absolute used capacity = 0.0 % ; Queue's Absolute max capacity = 100.0 % ; ]> but was:<[]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.hadoop.mapred.TestNetworkedJob.testNetworkedJob(TestNetworkedJob.java:174)
- is broken by
-
YARN-3946 Update exact reason as to why a submitted app is in ACCEPTED state to app's diagnostic message
-
- Resolved
-
- is duplicated by
-
MAPREDUCE-6623 TestRMNMInfo and TestNetworkedJob fails in trunk
-
- Resolved
-