attilapiros commented on issue #23801: [SPARK-26891][YARN] Fixing flaky test in 
YarnSchedulerBackendSuite
URL: https://github.com/apache/spark/pull/23801#issuecomment-464179868
 
 
   @vanzin in your PR [at the failed 
test](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/102369/testReport/org.apache.spark.scheduler.cluster/YarnSchedulerBackendSuite/RequestExecutors_reflects_node_blacklist_and_is_serializable/
   ) the exception's stacktrace was:
   
   ```
   at 
org.apache.spark.scheduler.cluster.YarnSchedulerBackendSuite.$anonfun$new$4(YarnSchedulerBackendSuite.scala:54)
        at scala.collection.Iterator.foreach(Iterator.scala:941)
        at scala.collection.Iterator.foreach$(Iterator.scala:941)
        at scala.collection.AbstractIterator.foreach(Iterator.scala:1429)
        at scala.collection.IterableLike.foreach(IterableLike.scala:74)
        at scala.collection.IterableLike.foreach$(IterableLike.scala:73)
        at scala.collection.AbstractIterable.foreach(Iterable.scala:56)
        at 
org.apache.spark.scheduler.cluster.YarnSchedulerBackendSuite.$anonfun$new$3(YarnSchedulerBackendSuite.scala:48)
        at scala.collection.immutable.Range.foreach$mVc$sp(Range.scala:158)
        at 
org.apache.spark.scheduler.cluster.YarnSchedulerBackendSuite.$anonfun$new$2(YarnSchedulerBackendSuite.scala:47)
   ```
    Based on the exception the problematic line is 
(YarnSchedulerBackendSuite.scala:54): 
   
   ```
         when(sched.nodeBlacklist()).thenReturn(blacklist)      
   ```
   
   I see there is SparkContext access in the 2nd test as well but I do not see 
failures for that one. On the other hand I have seen this failed more then 
once. 
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to