Skip to content
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

debug cache #17377

Merged
merged 23 commits into from
Sep 8, 2023
Merged

debug cache #17377

merged 23 commits into from
Sep 8, 2023

Conversation

garyverhaegen-da
Copy link
Contributor

No description provided.

@garyverhaegen-da garyverhaegen-da marked this pull request as draft September 7, 2023 13:11
@@ -83,5 +82,4 @@ if ($env:SKIP_TESTS -ceq "False") {
`-`-experimental_profile_include_target_label `
`-`-build_event_json_file test-events.json `
`-`-build_event_publish_all_actions `
`-`-experimental_execution_log_file ${ARTIFACT_DIRS}/logs/test_execution_windows_$env:SYSTEM_JOBATTEMPT.log `
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The binary execution log is basically useless: as far as I know nobody ever looks at it, and I don't seem to be able to build the parser for it. Trying to get the JSON execution log crashes the build on an OOM.

condition: and(succeededOrFailed(),
or(eq(${{parameters.is_release}}, 'false'),
ne('${{parameters.name}}', 'm1')))

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JSON execution logs are created pre-gzipped by Bazel, so there's little benefit to re-gzipping them.

"rev": "3a86856a13c88c8c64ea32082a851fefc79aa700",
"sha256": "04dd4g24061p8sw922zjickahqwn3wa9l3j5qllfzp5n6dy9is16"
"rev": "9a82a9b5248919805a2400266ebd881d5783df2a",
"sha256": "142x1zq3cjadgmvfv0paydlq268pfinllqpq2vl0vxwdiq2nr9iz"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the heart of this change: it looks like Bazel 5.2.0 is simply broken, so I'm bumping to 5.3.2.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@akrmn akrmn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you so much for figuring this out!

@garyverhaegen-da garyverhaegen-da merged commit 4bf7693 into main Sep 8, 2023
@garyverhaegen-da garyverhaegen-da deleted the debug-cache branch September 8, 2023 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants