Test Result : TaskSetManagerSuite

0 failures (±0)
51 tests (+1)
Took 6.6 sec.

All Tests

Test nameDurationStatus
Ensure TaskSetManager is usable after addition of levels48 msPassed
Executors exit for reason unrelated to currently running tasks43 msPassed
Kill other task attempts when one attempt belonging to the same task succeeds54 msPassed
Killing speculative tasks does not count towards aborting the taskset59 msPassed
Not serializable exception thrown if the task cannot be serialized44 msPassed
SPARK-13343 speculative tasks that didn't commit shouldn't be marked as success52 msPassed
SPARK-13704 Rack Resolution is done with a batch of de-duped hosts69 msPassed
SPARK-17894: Verify TaskSetManagers for different stage attempts have unique names39 msPassed
SPARK-19868: DagScheduler only notified of taskEnd when state is ready0.12 secPassed
SPARK-21563 context's added jars shouldn't change mid-TaskSet52 msPassed
SPARK-24677: Avoid NoSuchElementException from MedianHeap51 msPassed
SPARK-24755 Executor loss can cause task to not be resubmitted61 msPassed
SPARK-26755 Ensure that a speculative task is submitted only once for execution49 msPassed
SPARK-26755 Ensure that a speculative task obeys original locality preferences46 msPassed
SPARK-29976 Regular speculation configs should still take effect even when a threshold is provided39 msPassed
SPARK-29976 when a speculation time threshold is provided, should not speculative if there are too many tasks in the stage even though time threshold is provided46 msPassed
SPARK-29976 when a speculation time threshold is provided, should speculative run the task even if there are not enough successful runs, total tasks: 146 msPassed
SPARK-29976 when a speculation time threshold is provided, should speculative run the task even if there are not enough successful runs, total tasks: 243 msPassed
SPARK-29976: when the speculation time threshold is not provided,don't speculative run if there are not enough successful runs, total tasks: 147 msPassed
SPARK-29976: when the speculation time threshold is not provided,don't speculative run if there are not enough successful runs, total tasks: 252 msPassed
SPARK-31837: Shift to the new highest locality level if there is when recomputeLocality50 msPassed
SPARK-4939: no-pref tasks should be scheduled after process-local tasks finished35 msPassed
SPARK-4939: node-local tasks should be scheduled right after process-local tasks finished35 msPassed
TaskOutputFileAlreadyExistException lead to task set abortion48 msPassed
TaskSet with no preferences42 msPassed
TaskSetManager passes task resource along43 msPassed
Test TaskLocation for different host type1 msPassed
Test that locations with HDFSCacheTaskLocation are treated as PROCESS_LOCAL52 msPassed
[SPARK-13931] taskSetManager should not send Resubmitted tasks after being a zombie55 msPassed
[SPARK-22074] Task killed by other attempt task should not be resubmitted52 msPassed
abort the job if total size of results is too large1.4 secPassed
basic delay scheduling40 msPassed
cores due to standalone settings, speculate if there is only one task in the stage39 msPassed
delay scheduling with failed hosts51 msPassed
delay scheduling with fallback50 msPassed
do not emit warning when serialized task is small53 msPassed
don't update blacklist for shuffle-fetch failures, preemption, denied commits, or killed tasks49 msPassed
emit warning when serialized task is large42 msPassed
executors should be blacklisted after task failure, in spite of locality preferences47 msPassed
multiple offers with no preferences44 msPassed
new executors get added and lost48 msPassed
node-local tasks should be scheduled right away when there are only node-local and no-preference tasks43 msPassed
repeated failures lead to task set abortion52 msPassed
reset2.8 secPassed
skip unsatisfiable locality levels50 msPassed
speculative and noPref task should be scheduled after node-local44 msPassed
task result lost39 msPassed
test RACK_LOCAL tasks52 msPassed
update application blacklist for shuffle-fetch49 msPassed
update blacklist before adding pending task to avoid race condition56 msPassed
we do not need to delay scheduling when we only have noPref tasks in the queue48 msPassed