Description of the bug:

In Bazel 7, when using --experimental_merged_skyframe_analysis_execution (the default), and using bazel coverage (but not bazel test), test results are delayed until the end of the build. If using --noexperimental_merged_skyframe_analysis_execution, or using bazel test, test results appear as soon as the tests are done running.

Which category does this issue belong to?

Core

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

$ git checkout git@github.com:bazelbuild/bazel.git
$ cd bazel
$ USE_BAZEL_VERSION=7.0.2 bazel coverage --bes_results_url=https://app.buildbuddy.io/invocation/ --bes_backend=grpcs://remote.buildbuddy.io --cache_test_results=no //src/test/java/com/google/devtools/build/lib/...
$ USE_BAZEL_VERSION=7.0.2 bazel clean
$ USE_BAZEL_VERSION=7.0.2 bazel coverage --bes_results_url=https://app.buildbuddy.io/invocation/ --bes_backend=grpcs://remote.buildbuddy.io --cache_test_results=no --noexperimental_merged_skyframe_analysis_execution //src/test/java/com/google/devtools/build/lib/...

In the first run, testResult events aren't published until the end of the build. In the second run they are published as soon as they are done running.

Which operating system are you running Bazel on?

macOS

What is the output of bazel info release?

release 7.0.2

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 ?

No response

Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

No response

Have you found anything relevant by searching the web?

I saw the message in 37247d5, and it seems that there was a change regarding how the combined report was generated. Maybe that is delaying these related events?

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

No response