Closed joeljeske closed 2 months ago
@joeljeske Could you please provide sample code to reproduce this issue? Thanks
I ran bazel info peak-heap-size used-heap-size max-heap-size used-heap-size-after-gc
in a loop with --remote_executor
set, but I couldn't reproduce it. There's probably some other flag that need to be set? Please reopen with a self-contained repro.
Description of the bug:
Occasionally, I receive the following error stack when I run
bazel info peak-heap-size used-heap-size max-heap-size used-heap-size-after-gc
.Bazel still returns the proper values for those info properties, but it also prints this stack to stderr ~5% of the time. I do have --remote_executor set.
Which category does this issue belong to?
Remote Execution
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?
No response
What is the output of
bazel info release
?release 7.1.1
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
?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