You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2019/11/03 19:22:00 UTC

[jira] [Resolved] (SPARK-29733) Wrong order of assertEquals parameters

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

Dongjoon Hyun resolved SPARK-29733.
-----------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

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

> Wrong order of assertEquals parameters
> --------------------------------------
>
>                 Key: SPARK-29733
>                 URL: https://issues.apache.org/jira/browse/SPARK-29733
>             Project: Spark
>          Issue Type: Test
>          Components: ML, Spark Core, SQL, Structured Streaming
>    Affects Versions: 2.4.4
>            Reporter: Maxim Gekk
>            Assignee: Maxim Gekk
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> The assertEquals() requires the expected value as the first parameter, for instance: https://junit.org/junit4/javadoc/4.12/org/junit/Assert.html#assertEquals(long,%20long)
> but in some places the expected value is passed as the second parameter that confuses when such assert fails.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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