experimental_execution_graph_log_path doesn't support relative paths

[emaxx-google]

Description of the bug:

When specifying a relative path, like --experimental_execution_graph_log_path=graph.log, the resulting file (in this example, graph.log) ends up being created not in the project's directory, but rather in ~/.cache/bazel/_bazel_<user>/<hash>/.

This is surprising and different from how other flags, like --profile or --execution_log_binary_file, work.

1. The workaround is to pass an absolute file path to this flag.

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.

bazel build <...> \
    --experimental_enable_execution_graph_log \
    --experimental_execution_graph_log_dep_type=all \
    --experimental_execution_graph_log_path=graph.log

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 7.1.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 ?

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?

No response

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

No response