We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider this invocation: https://btx.cloud.google.com/invocations/7f6a08b3-606a-44f5-99aa-6521a88de319/log
The elapsed time as logged is a little over 7 minutes:
INFO: Elapsed time: 428.388s, Critical Path: 11.30s
However, when I upload the command.profile.gz (available in the Invocation Artifacts tab) to Perfetto, I see only about 4 minutes and 30 seconds of profile data: https://ui.perfetto.dev/#!/?s=b032b2b7f81070f86acb8f0fcfa831a0397898a5
command.profile.gz
@tjgq
Remote Execution
No response
MacOS
bazel info release
development version
(@non-git)
I'm using 1ff5af18d045e8f30a2a0367470db4e8225a785c, fetched by Bazelisk via .bazelversion.
1ff5af18d045e8f30a2a0367470db4e8225a785c
.bazelversion
git remote get-url origin; git rev-parse HEAD
The text was updated successfully, but these errors were encountered:
sgowroji
iancha1992
satyanandak
No branches or pull requests
Description of the bug:
Consider this invocation: https://btx.cloud.google.com/invocations/7f6a08b3-606a-44f5-99aa-6521a88de319/log
The elapsed time as logged is a little over 7 minutes:
However, when I upload the
command.profile.gz
(available in the Invocation Artifacts tab) to Perfetto, I see only about 4 minutes and 30 seconds of profile data: https://ui.perfetto.dev/#!/?s=b032b2b7f81070f86acb8f0fcfa831a0397898a5@tjgq
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?
MacOS
What is the output of
bazel info release
?development version
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.I'm using
1ff5af18d045e8f30a2a0367470db4e8225a785c
, fetched by Bazelisk via.bazelversion
.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
The text was updated successfully, but these errors were encountered: