Github user JoshRosen commented on the pull request: https://github.com/apache/spark/pull/7385#issuecomment-122322859 Ah, interesting: it looks a race condition in the existing JobWaiter has led to flakiness in a unit test. Here's the Jenkins failure: https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-SBT/lastCompletedBuild/AMPLAB_JENKINS_BUILD_PROFILE=hadoop1.0,label=centos/testReport/org.apache.spark.scheduler/DAGSchedulerSuite/misbehaved_resultHandler_should_not_crash_DAGScheduler_and_SparkContext/ > java.lang.UnsupportedOperationException: taskSucceeded() called on a finished JobWaiter was not instance of org.apache.spark.scheduler.DAGSchedulerSuiteDummyException
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org