-
Notifications
You must be signed in to change notification settings - Fork 781
New issue
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
[ci] Produce and upload bazel execution logs #20318
Draft
pamaury
wants to merge
9
commits into
lowRISC:master
Choose a base branch
from
pamaury:bazel_cache_investigate
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pamaury
force-pushed
the
bazel_cache_investigate
branch
from
November 10, 2023 18:51
0e15c51
to
9701dd8
Compare
This looks interesting! However, it appears bazel struggles to handle the data within whatever memory size restrictions we have set up (not sure if it's physical or JVM-limited). I wonder why.
|
pamaury
force-pushed
the
bazel_cache_investigate
branch
from
November 11, 2023 02:31
9701dd8
to
7333ba7
Compare
I think this is a know problem and, in a typical bazel fashion, there is a flag for it ! that may help in certain circumstances... |
The execution log is 1.8GB large :-o |
Execution logs can be used to debug caching and understand better what bazel is doing. This commit introduces a general mecanism to upload those logs. Only convert the SW build and test step for now. Signed-off-by: Amaury Pouly <amaury.pouly@lowrisc.org>
pamaury
force-pushed
the
bazel_cache_investigate
branch
5 times, most recently
from
January 16, 2024 11:18
cef9594
to
400cd90
Compare
Signed-off-by: Amaury Pouly <amaury.pouly@lowrisc.org>
pamaury
force-pushed
the
bazel_cache_investigate
branch
from
January 16, 2024 11:39
400cd90
to
f2a4caa
Compare
pamaury
force-pushed
the
bazel_cache_investigate
branch
from
January 16, 2024 16:57
9d00bdd
to
f1023ac
Compare
pamaury
force-pushed
the
bazel_cache_investigate
branch
from
January 16, 2024 17:04
f1023ac
to
ba29580
Compare
Signed-off-by: Amaury Pouly <amaury.pouly@lowrisc.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Execution logs can be used to debug caching and understand better what bazel is doing. This commit introduces a general mecanism to upload those logs. Only convert the SW build and test step for now.