[GH] (pekko/removeJunit4): Workflow run "Binary Compatibility" failed!

[GitBox <gi...@apache.org>]

The GitHub Actions job "Binary Compatibility" on pekko.git/removeJunit4 has failed.
Run started by GitHub user He-Pin (triggered by He-Pin).

Head commit for run:
3cfe856a80ee70d134a33578068c73b1526bc13b / He-Pin <he...@gmail.com>
feat: Migrate all Java unit tests from JUnit 4 to JUnit 5 (Jupiter)

Motivation:
JUnit 4 has reached end-of-life and JUnit 5 (Jupiter) provides significant
improvements. The project already uses jupiter-engine 6.0.3 and has existing
JUnitJupiter-named infrastructure. This migration aligns all test code with
the modern Jupiter naming convention.

Modification:
- Replace @ClassRule/@Rule with @RegisterExtension using
  PekkoJUnitJupiterActorSystemResource (renamed from JUnit5 variant)
- Replace StreamTest5 base class with StreamTestJupiter
- Replace TestKitJUnit5Extension with TestKitJUnitJupiterExtension
- Replace @JUnit5TestKit with @JUnitJupiterTestKit annotation
- Replace JUnit5TestKitBuilder with JUnitJupiterTestKitBuilder
- Remove extends JUnitSuite (JUnit 4 base class)
- Migrate Assert to Assertions, @Test(expected=...) to assertThrows()
- Add synchronized lifecycle methods for thread safety
- Remove printStackTrace from error handling
- 105 files changed across all test modules

Result:
All Java unit tests now use JUnit Jupiter APIs with consistent JUnitJupiter
naming convention. JUnit 4 support APIs remain available for downstream users.
All tests pass locally.

References:
- PR review feedback: https://github.com/apache/pekko/pull/2724#issuecomment-4063849648
- JUnit 5 User Guide: https://junit.org/junit5/docs/current/user-guide/

Report URL: https://github.com/apache/pekko/actions/runs/23203578634

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org