celeborn/client/src/test
zwangsheng 6c2fdf7477
[CELEBORN-1188][TEST] Using JUnit function instead of java assert
### What changes were proposed in this pull request?
Using Junit function instead of java assert.

### Why are the changes needed?
When java assert fail, will throw AssertException, which is hard to find diff.

![截屏2023-12-20 10 34 52](https://github.com/apache/incubator-celeborn/assets/52876270/b36421a5-64e1-4717-a6d4-3b08db403293)

Instead, when we use junit assert, we can clearly find diff.

![截屏2023-12-20 11 17 21](https://github.com/apache/incubator-celeborn/assets/52876270/ce39fa20-e9ab-4419-a4ca-62c4157e4b2c)

### Does this PR introduce _any_ user-facing change?
NO, only test changed

### How was this patch tested?
Run CI

Closes #2173 from zwangsheng/CELEBORN-1188.

Authored-by: zwangsheng <binjieyang@apache.org>
Signed-off-by: Cheng Pan <chengpan@apache.org>
2023-12-20 21:20:38 +08:00
..
java/org/apache/celeborn/client [CELEBORN-1188][TEST] Using JUnit function instead of java assert 2023-12-20 21:20:38 +08:00
resources [CELEBORN-1022][TEST] Update log level from FATAL to ERROR for console output in unit tests 2023-10-09 15:56:05 +08:00
scala/org/apache/celeborn/client [CELEBORN-1167] Avoid calling parmap when destroy slots 2023-12-15 18:30:31 +08:00