[bazel] Reintroduce bazelified ruby and python tests#34033
Merged
jtattermusch merged 3 commits intogrpc:masterfrom Aug 16, 2023
Merged
[bazel] Reintroduce bazelified ruby and python tests#34033jtattermusch merged 3 commits intogrpc:masterfrom
jtattermusch merged 3 commits intogrpc:masterfrom
Conversation
jtattermusch
added
the
release notes: no
grpc-checks
bot
added
per-call-memory/neutral
per-channel-memory/neutral
bloat/none
labels
Contributor
Author
|
Non bazel test run is green: https://source.cloud.google.com/results/invocations/90d99b8b-6496-4b99-8703-1fb6384d5761 |
XuanWang-Amos
approved these changes
Aug 16, 2023
copybara-service
bot
added
the
imported
jtattermusch
added a commit
that referenced
this pull request
Aug 16, 2023
…grade ccache (#34035) Based on #34033 Bunch of cleanup and rebuilding many docker images from scratch - consolidate the workaround for "dubious ownership" issue reported by git. Other team members have run into this recently and used similar but not identical workarounds so some cleanup is due. - rebuilding many images increases the chance that we fix the "dubious ownership" git issue early on rather than later on in the one-at-a-time fashion in the future (and the former will prevent many teammembers from wasting time on this weird issue). - Newer version of ccache is needed for some portability tests to be able to benefit from caching (e.g. the GCC 12 portability test to get benefits of local disk caching) - this is a prerequisite for reenabling the bazelified gcc12 portability test. - upgrade node interop images to debian:11 (since debian jessie is long past EOL).
eugeneo
pushed a commit
to eugeneo/grpc
that referenced
this pull request
Aug 21, 2023
Reintroduce grpc#33959. I added a fix for the python arm64 build (which is the reason why the change has been reverted earlier).
eugeneo
pushed a commit
to eugeneo/grpc
that referenced
this pull request
Aug 21, 2023
…grade ccache (grpc#34035) Based on grpc#34033 Bunch of cleanup and rebuilding many docker images from scratch - consolidate the workaround for "dubious ownership" issue reported by git. Other team members have run into this recently and used similar but not identical workarounds so some cleanup is due. - rebuilding many images increases the chance that we fix the "dubious ownership" git issue early on rather than later on in the one-at-a-time fashion in the future (and the former will prevent many teammembers from wasting time on this weird issue). - Newer version of ccache is needed for some portability tests to be able to benefit from caching (e.g. the GCC 12 portability test to get benefits of local disk caching) - this is a prerequisite for reenabling the bazelified gcc12 portability test. - upgrade node interop images to debian:11 (since debian jessie is long past EOL).
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Reintroduce #33959.
I added a fix for the python arm64 build (which is the reason why the change has been reverted earlier).