Details for spark-master-test-sbt-hadoop-2.6-ubuntu-test build #1262

View on Jenkins

Duration
317 minutes
Start time
2018-10-19 18:48:17 ()
Commit
43717dee570dc41d71f0b27b8939f6297a029a02
Executor
research-jenkins-worker-07
Status
FAILURE

Failed tests

org.apache.spark.BarrierStageOnSubmittedSuite: submit a barrier ShuffleMapStage that requires more slots than current total under local-cluster mode 10518 ms
org.apache.spark.MapOutputTrackerSuite: (It is not a test it is a sbt.testing.SuiteSelector) 0 ms
org.apache.spark.StatusTrackerSuite: basic status API usage 26 ms
org.apache.spark.StatusTrackerSuite: getJobIdsForGroup() 25 ms
org.apache.spark.StatusTrackerSuite: getJobIdsForGroup() with takeAsync() 25 ms
org.apache.spark.StatusTrackerSuite: getJobIdsForGroup() with takeAsync() across multiple partitions 26 ms
org.apache.spark.scheduler.EventLoggingListenerSuite: End-to-end event logging with compression 998363 ms
org.apache.spark.scheduler.TaskSetManagerSuite: abort the job if total size of results is too large 6073 ms
org.apache.spark.scheduler.TaskSetManagerSuite: [SPARK-13931] taskSetManager should not send Resubmitted tasks after being a zombie 1339 ms
org.apache.spark.scheduler.TaskSetManagerSuite: [SPARK-22074] Task killed by other attempt task should not be resubmitted 26 ms
org.apache.spark.scheduler.TaskSetManagerSuite: speculative and noPref task should be scheduled after node-local 26 ms
org.apache.spark.scheduler.TaskSetManagerSuite: node-local tasks should be scheduled right away when there are only node-local and no-preference tasks 475 ms
org.apache.spark.scheduler.TaskSetManagerSuite: SPARK-4939: node-local tasks should be scheduled right after process-local tasks finished 25 ms
org.apache.spark.scheduler.TaskSetManagerSuite: SPARK-4939: no-pref tasks should be scheduled after process-local tasks finished 25 ms
org.apache.spark.scheduler.TaskSetManagerSuite: Ensure TaskSetManager is usable after addition of levels 25 ms
org.apache.spark.scheduler.TaskSetManagerSuite: Test that locations with HDFSCacheTaskLocation are treated as PROCESS_LOCAL 25 ms
org.apache.spark.scheduler.TaskSetManagerSuite: Kill other task attempts when one attempt belonging to the same task succeeds 29 ms
org.apache.spark.scheduler.TaskSetManagerSuite: Killing speculative tasks does not count towards aborting the taskset 26 ms
org.apache.spark.scheduler.TaskSetManagerSuite: SPARK-19868: DagScheduler only notified of taskEnd when state is ready 27 ms
org.apache.spark.scheduler.TaskSetManagerSuite: SPARK-17894: Verify TaskSetManagers for different stage attempts have unique names 29 ms
org.apache.spark.scheduler.TaskSetManagerSuite: don't update blacklist for shuffle-fetch failures, preemption, denied commits, or killed tasks 25 ms
org.apache.spark.scheduler.TaskSetManagerSuite: update application blacklist for shuffle-fetch 25 ms
org.apache.spark.scheduler.TaskSetManagerSuite: update blacklist before adding pending task to avoid race condition 42 ms
org.apache.spark.scheduler.TaskSetManagerSuite: SPARK-21563 context's added jars shouldn't change mid-TaskSet 26 ms
org.apache.spark.scheduler.TaskSetManagerSuite: [SPARK-24677] Avoid NoSuchElementException from MedianHeap 26 ms
org.apache.spark.scheduler.TaskSetManagerSuite: SPARK-24755 Executor loss can cause task to not be resubmitted 26 ms
org.apache.spark.scheduler.TaskSetManagerSuite: SPARK-13343 speculative tasks that didn't commit shouldn't be marked as success 26 ms

Test time report

Right click on the visualization to go back up a level. Click on a node to expand it. Hover over a node to see the combined duration of tests under that node.