[improve][build] Disable test retry when running tests in IntelliJ#25814
Merged
Conversation
nodece
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
When running tests in IntelliJ, the current Gradle configuration re-runs failed tests via the
testRetryCountsystem property (default1). This is undesirable when running tests manually in the IDE: a developer triggering a single test expects to see its actual failure, not a retried run that obscures the original error or flakiness.IntelliJ delegates test execution to Gradle, and it can be detected at build configuration time via the
idea.activesystem property that IntelliJ sets when invoking Gradle.Modifications
build-logic/conventions/src/main/kotlin/pulsar.java-conventions.gradle.kts: whenidea.active=true, defaulttestRetryCountto0instead of1. An explicit-PtestRetryCount=...Gradle property still takes precedence.tests/integration/build.gradle.kts: same change applied to theintegrationTesttask.CLI / CI behavior is unchanged because
idea.activeis not set there.Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts: