Passing --runs_per_test via the run configuration is not respected

[srdo-humio]

Description of the bug:

For some reason, this plugin passes --runs_per_test=1 as part of fixed flags passed to Bazel, here

intellij/base/src/com/google/idea/blaze/base/run/confighandler/BlazeCommandGenericRunConfigurationRunner.java

Line 200 in e914b0d

.add("--runs_per_test=1")

As these fixed flags end up on the command line after flags specified by the user's run configuration, this prevents configuring Intellij to run a single test multiple times. This is inconvenient when trying to reproduce flaky test failures in the IDE.

For example, if I add --runs_per_test=100 to a run configuration, the resulting command line looks like this:

... --runs_per_test=100 --test_runner_fail_fast --runs_per_test=1 --flaky_test_attempts=1

which ends up overriding my configuration.

I don't really understand why the plugin needs to set either --runs_per_test=1 or --flaky_test_attempts=1, shouldn't that be left to the user to define in either the run configuration, or the project settings?

Which category does this issue belong to?

Intellij

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Open a run configuration for a test in Intellij, and add --runs_per_test=100 to the Bazel flags. Run the test. See that the command line executed ends up setting --runs_per_test=1.

Which Intellij IDE are you using? Please provide the specific version.

2025.2.4

What programming languages and tools are you using? Please provide specific versions.

Scala 2.13, Scalatest 3.2.19

What Bazel plugin version are you using?

2025.2.48

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response