`--test_output=streamed` does not stream the logs when executing remotely

Description of the bug:

If running a test with a remote executor

bazel test --remote_executor=grpcs://remotebuildexecution.googleapis.com --test_output=streamed //path/to:test 

No logs are actually streamed to the terminal:

INFO: Analyzed target //incode/experimental/users/alexanderfaxa:sleep_forever_test (0 packages loaded, 0 targets configured).
[4 / 5] Testing //experimental/users/faximan:sleep_forever_test; 28s
# nothing

Eventually, the test times out and then dumps the whole log to my terminal. If I ctrl-c abort the process while the test is running, the logs are as far as I know lost forever.

Which category does this issue belong to?

Remote Execution

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

No response

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 8.4.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

Private repo

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

There is https://github.com/bazelbuild/bazel/issues/19428 which is somewhat related.

Some people there are wondering whether --test_output=streamed will force local execution. In my experience it does not.

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

No response