You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sean R. Owen (Jira)" <ji...@apache.org> on 2022/03/22 23:11:00 UTC

[jira] [Resolved] (SPARK-38619) Clean up Junit api usage in scalatest

     [ https://issues.apache.org/jira/browse/SPARK-38619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean R. Owen resolved SPARK-38619.
----------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

Issue resolved by pull request 35929
[https://github.com/apache/spark/pull/35929]

> Clean up Junit api usage in scalatest
> -------------------------------------
>
>                 Key: SPARK-38619
>                 URL: https://issues.apache.org/jira/browse/SPARK-38619
>             Project: Spark
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 3.4.0
>            Reporter: Yang Jie
>            Assignee: Yang Jie
>            Priority: Minor
>             Fix For: 3.4.0
>
>
> There are some Junit api usage in scalatest, for example
>  
> {code:java}
>   test("SPARK-31422: getMemoryStatus should not fail after BlockManagerMaster stops") {
>     val bmm = new BlockManagerMaster(null, null, new SparkConf, true)
>     assertTrue(bmm.getMemoryStatus.isEmpty)
>   } {code}
> `assertTrue` is junit api 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org