Skip to content

IGNITE-28738 RU test: small code-quality cleanups#2

Merged
wernerdv merged 1 commit into
wernerdv:testcontainersfrom
anton-vinogradov:ignite-28738-quality
Jun 27, 2026
Merged

IGNITE-28738 RU test: small code-quality cleanups#2
wernerdv merged 1 commit into
wernerdv:testcontainersfrom
anton-vinogradov:ignite-28738-quality

Conversation

@anton-vinogradov

Copy link
Copy Markdown

Small, behavior-preserving code-quality cleanups on top of the RU testcontainers test. Verified green end-to-end on macOS (IgniteRebalanceOnUpgradeTest, 1 test, ~357s) and test-compile is clean.

Changes

  • IgniteContainer.stop() — drop the unconditional "Ignite node … shut down gracefully." log. The image entrypoint does not forward SIGTERM, so the await times out and the node is force-stopped via super.stop(); the message directly contradicted the preceding "Proceeding with forceful stop." warning.
  • IgniteContainer.testClassesJar() — null-check File.listFiles() (returns null on an unreadable directory) so a missing class directory fails with a clear IOException instead of an NPE inside the loop.
  • IgniteRebalanceOnUpgradeTest — compare the post-put value as a boxed Integer (the get-loop already does this), so a missing key fails the assertion instead of NPE-ing on unboxing.
  • Scope the "bind communication to loopback" comment to macOS (on Linux it binds to 0.0.0.0) so it no longer contradicts the code, and drop a trailing-whitespace blank line.

No behavioral change on the macOS path.

🤖 Generated with Claude Code

- IgniteContainer.stop(): drop the unconditional "shut down gracefully"
  log. The image entrypoint does not forward SIGTERM, so the await times
  out and the node is force-stopped via super.stop(); the message
  contradicted the preceding "Proceeding with forceful stop." warning.

- IgniteContainer.testClassesJar(): null-check File.listFiles() (returns
  null on an unreadable dir) so a missing class directory fails with a
  clear IOException instead of an NPE in the loop.

- IgniteRebalanceOnUpgradeTest: compare the post-put value as a boxed
  Integer too (the get(1000)-loop already does), so a missing key fails
  the assertion instead of NPE-ing on unboxing.

- Scope the "bind communication to loopback" comment to macOS (on Linux
  it binds to 0.0.0.0) and drop a trailing-whitespace blank line.

No behavioral change on the macOS path.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@wernerdv wernerdv merged commit 916ad1c into wernerdv:testcontainers Jun 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants