Details for spark-master-test-sbt-hadoop-2.6 build #1620

View on Jenkins

Duration
118 minutes
Start time
2016-09-13 09:45:16 ()
Commit
46f5c201e70053635bdeab4984ba1b649478bd12
Executor
amp-jenkins-worker-06
Status
FAILURE

Failed tests

org.apache.spark.PartitioningSuite: (It is not a test) 47 ms
org.apache.spark.SparkContextSuite: addFile can be called twice with same file in non-local-mode (SPARK-16787) 21 ms
org.apache.spark.SparkContextSuite: Cancelling job group should not cause SparkContext to shutdown (SPARK-6414) 56 ms
org.apache.spark.SparkContextSuite: Comma separated paths for newAPIHadoopFile/wholeTextFiles/binaryFiles (SPARK-7155) 29 ms
org.apache.spark.SparkContextSuite: Default path for file based RDDs is properly set (SPARK-12517) 21 ms
org.apache.spark.SparkContextSuite: stop() must not throw any exception 26 ms
org.apache.spark.SparkContextSuite: No exception when both num-executors and dynamic allocation set 27 ms
org.apache.spark.SparkContextSuite: localProperties are inherited by spawned threads 24 ms
org.apache.spark.SparkContextSuite: localProperties do not cross-talk between threads 22 ms
org.apache.spark.SparkContextSuite: log level case-insensitive and reset log level 23 ms
org.apache.spark.scheduler.BlacklistIntegrationSuite: If preferred node is bad, without blacklist job will fail 36 ms
org.apache.spark.scheduler.BlacklistIntegrationSuite: (It is not a test) 40 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: Scheduler does not always schedule tasks on the same workers 40 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: Scheduler correctly accounts for multiple CPUs per task 33 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: Scheduler does not crash when tasks are not serializable 26 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: refuse to schedule concurrent attempts for the same stage (SPARK-8103) 26 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: don't schedule more tasks after a taskset is zombie 26 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: if a zombie attempt finishes, continue scheduling tasks for non-zombie attempts 28 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: tasks are not re-scheduled while executor loss reason is pending 28 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: abort stage if executor loss results in unschedulability from previously failed tasks 56 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: don't abort if there is an executor available, though it hasn't had scheduled tasks yet 30 ms
org.apache.spark.scheduler.TaskSchedulerImplSuite: SPARK-16106 locality levels updated if executor added to existing host 26 ms
org.apache.spark.storage.DiskBlockManagerSuite: (It is not a test) 3 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.