.blazerc mentioned (wrong filename) on import error at bazel startup

[peakschris]

Description of the bug:

If a .bazelrc file has a error due to failed import, the following message is displayed:

[FATAL 05:46:36.066 src/main/cpp/blaze.cc:1104] Unexpected error reading .blazerc file 'd:\workdir\javaproject2/out/bazelrc/imported.bazelrc':

The error should reference .bazelrc not .blazerc

Which category does this issue belong to?

No response

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?

windows

What is the output of bazel info release?

7.2.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

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?

No response

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

No response

[fmeum]

@bazel-io fork 7.3.0

[iancha1992]

A fix for this issue has been included in Bazel 7.3.0 RC1. Please test out the release candidate and report any issues as soon as possible.
If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=7.3.0rc1. Thanks!