Open mattyclarkson opened 2 months ago
Can you rerun with --verbose_failures
so we have a stacktrace?
I think the error that I am seeing here is also related.
Can you rerun with
--verbose_failures
so we have a stacktrace?
Attempting to get a stack trace but the conditioning for it triggering are challenging, especially locally. We should catch one soon on the CI and I'll update.
Description of the bug:
rules_git
, when checking out the working directory into adeclare_directory
will occasionally report:GitLab CI Log, Buildkite Log.
Which category does this issue belong to?
Local Execution, Remote Execution, Rules API
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
The bug is flaky, so repeat the test as one sees fit.
Which operating system are you running Bazel on?
Linux
What is the output of
bazel info release
?release 7.2.1rc2
If
bazel info release
returnsdevelopment 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
?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?
22151 is a bug in a similar area
Any other information, logs, or outputs that you want to share?
No response