Uh oh!
There was an error while loading. Please reload this page.
[MINOR][TESTS] Replace JVM assert with JUnit Assert in tests - #26581
[MINOR][TESTS] Replace JVM assert with JUnit Assert in tests#26581srowen wants to merge 2 commits into
Conversation
dongjoon-hyun
commented
Nov 18, 2019
Is this all? It seems that we have more instances. |
srowen
commented
Nov 18, 2019
That's all IntelliJ found in the Java test code. There may be some in non-test code, but some are possibly legitimate. There are, I think, cases where assert() is used for argument checking in non-test code and that's not really what it's for, but a separate thing. Yeah there are some in Scala tests too, I'll fix those. They're not obvious as scalatest uses assert() too, but we can look for use of scala.Predef.assert() |
SparkQA
commented
Nov 18, 2019
Test build #114032 has finished for PR 26581 at commit
|
SparkQA
commented
Nov 18, 2019
Test build #114027 has finished for PR 26581 at commit
|
srowen
commented
Nov 18, 2019
(PS to be clear the latest test failed; its result just came first. I'll investigate) |
dongjoon-hyun
commented
Nov 18, 2019
It seems that both Jenkins/GitHubAction fails due to |
SparkQA
commented
Nov 19, 2019
Test build #114040 has finished for PR 26581 at commit
|
HyukjinKwon
commented
Nov 19, 2019
retest this please |
SparkQA
commented
Nov 19, 2019
Test build #114056 has finished for PR 26581 at commit
|
srowen
commented
Nov 20, 2019
PS @dongjoon-hyun is this failure 'normal'? https://github.com/apache/spark/runs/311900764 Just can't download maven? |
SparkQA
commented
Nov 20, 2019
Test build #114167 has finished for PR 26581 at commit
|
Yes. It's a normal |
SparkQA
commented
Nov 20, 2019
Test build #114174 has finished for PR 26581 at commit
|
srowen
commented
Nov 20, 2019
Merged to master |
What changes were proposed in this pull request?
Use JUnit assertions in tests uniformly, not JVM assert() statements.
Why are the changes needed?
assert() statements do not produce as useful errors when they fail, and, if they were somehow disabled, would fail to test anything.
Does this PR introduce any user-facing change?
No. The assertion logic should be identical.
How was this patch tested?
Existing tests.