experimental_execution_log_compact_file with topleve flags fails with IOException while logging spawn:

[nkoroste]

Description of the bug:

With Bazel 7.2.1 if you have the following flags enabled

--experimental_execution_log_compact_file=compact_exec.log
--remote_download_outputs=toplevel

The build will fail with an IOException if you have an action that uses a directory as input/output. Example:

12:35:50 19:35:51 [Bazel] ERROR: /var/lib/jenkins/workspace/android/snapchat/platform/media/decoders/gav1-dynamic-feature/BUILD.bazel:4:11: Merging AAR embedded jars failed: IOException while logging spawn: /home/jenkins/Snapchat/Dev/.cache/bazel/x86_64/6f9c9cb8506de64f63094a5ee74046fa/execroot/__main__/bazel-out/arm64-v8a-fastbuild-android-ST-f6ab2eff499b/bin/platform/media/decoders/gav1-dynamic-feature/_aar/unzipped (No such file or directory)

or

21:54:30 [Bazel] ERROR: /Users/devicelab/Snapchat/Dev/.cache/bazel/arm64/200c81ba794154ad95d9a76cac3f836f/external/snap_client/src/composer_modules/src/composer/jasmine/BUILD.bazel:9:16: Linking external/snap_client/src/composer_modules/src/composer/jasmine/libjasmine_api_objc.a failed: IOException while logging spawn: /Users/devicelab/Snapchat/Dev/.cache/bazel/arm64/200c81ba794154ad95d9a76cac3f836f/execroot/phantom/bazel-out/ios_arm64-dbg-ios-arm64-min14.0-applebin_ios-ST-90933ed6271b/bin/external/snap_client/src/composer_modules/src/composer/jasmine/_objs/jasmine_api_objc/arc/debug_api_objc_srcs (No such file or directory)

This is similar to https://github.com/bazelbuild/bazel/issues/21820 and related to https://github.com/bazelbuild/bazel/pull/22253

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.

No response

Which operating system are you running Bazel on?

Mac and Linux

What is the output of bazel info release?

7.2.1

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

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?

This is similar to https://github.com/bazelbuild/bazel/issues/21820 and related to https://github.com/bazelbuild/bazel/pull/22253

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

No response