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

Fix remote spawn tests for remote_merkle_tree_cache=true #14300

Closed

Conversation

moroten
Copy link
Contributor

@moroten moroten commented Nov 19, 2021

When setting --experimental_remote_merkle_tree_cache=true as default and running the test suite, some errors became visible. This change fixes those errors.

When setting --experimental_remote_merkle_tree_cache=true as default and
running the test suite, some errors became visible. This change fixes
those errors.
@google-cla google-cla bot added the cla: yes label Nov 19, 2021
The tests did all pass on Github, so let's revert the default value.
@moroten moroten marked this pull request as ready for review November 22, 2021 08:29
@moroten moroten requested a review from a team as a code owner November 22, 2021 08:29
@bazel-io bazel-io closed this in d84f799 Nov 25, 2021
coeuvre pushed a commit to coeuvre/bazel that referenced this pull request Nov 25, 2021
When setting `--experimental_remote_merkle_tree_cache=true` as default and running the test suite, some errors became visible. This change fixes those errors.

Closes bazelbuild#14300.

PiperOrigin-RevId: 412274673
meteorcloudy pushed a commit that referenced this pull request Nov 25, 2021
When setting `--experimental_remote_merkle_tree_cache=true` as default and running the test suite, some errors became visible. This change fixes those errors.

Closes #14300.

PiperOrigin-RevId: 412274673

Co-authored-by: Fredrik Medley <fredrik.medley@gmail.com>
@coeuvre
Copy link
Member

coeuvre commented Nov 30, 2021

This is rolled back in 4256d46 because it breaks some internal tests.

@meteorcloudy
Copy link
Member

@coeuvre Hmm, should we also rollback this in the 5.0.0rc2? Or are we going to rollfoward with a fix?

@moroten
Copy link
Contributor Author

moroten commented Nov 30, 2021

This PR was not meant for 5.0, only for master. It is a preparation for potential default activation of the Merkle tree caching feature, but I'll leave it as is because I can't fix the Google internal tests.

Bencodes pushed a commit to Bencodes/bazel that referenced this pull request Jan 10, 2022
When setting `--experimental_remote_merkle_tree_cache=true` as default and running the test suite, some errors became visible. This change fixes those errors.

Closes bazelbuild#14300.

PiperOrigin-RevId: 412274673
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants