Github user vanzin commented on a diff in the pull request:

    https://github.com/apache/spark/pull/19041#discussion_r163055034
  
    --- Diff: 
core/src/test/scala/org/apache/spark/scheduler/CacheRecoveryIntegrationSuite.scala
 ---
    @@ -0,0 +1,136 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.spark.scheduler
    +
    +import scala.util.Try
    +
    +import org.scalatest.{BeforeAndAfterEach, Matchers}
    +import org.scalatest.concurrent.Eventually
    +import org.scalatest.time.{Seconds, Span}
    +
    +import org.apache.spark.{SparkConf, SparkContext, SparkFunSuite, TestUtils}
    +import org.apache.spark.internal.config._
    +import org.apache.spark.network.TransportContext
    +import org.apache.spark.network.netty.SparkTransportConf
    +import org.apache.spark.network.server.TransportServer
    +import org.apache.spark.network.shuffle.ExternalShuffleBlockHandler
    +import org.apache.spark.rdd.RDD
    +import org.apache.spark.storage._
    +
    +class CacheRecoveryIntegrationSuite
    --- End diff --
    
    I'm not too sure about what this suite is testing. You seem to be relying 
on the very short idle timeout to have the executors killed; but it doesn't 
seem like there a strong relation between your test code and which / how many 
executors will be killed as idle.
    
    Instead, shouldn't you explicitly be killing executors to verify that the 
data is being replicated?
    
    Or at least explain in a comment how this test is actually testing the 
functionality being added.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to