Conversation
|
FYI The toolchain problem is the same as in here: #25001 |
|
|
||
| set -ex | ||
|
|
||
| shopt -s nullglob |
There was a problem hiding this comment.
nit: why do you need this? same for the other .sh files.
| "x64_windows_msys": ":cc-compiler-x64_windows_msys", | ||
| "x64_windows": ":cc-compiler-x64_windows", | ||
| "armeabi-v7a": ":cc-compiler-armeabi-v7a", | ||
| "k8": ":_dummy_toolchain", |
There was a problem hiding this comment.
why the changes? this file is autogenerated AFAIK so I don't feel comfortable updating it manually.
Would regenerating the BUILD help?
go/rbe-windows-user-guide
| @@ -1,5 +1,5 @@ | |||
| #!/bin/bash | |||
| # Copyright 2017 gRPC authors. | |||
| # Copyright 2020 The gRPC authors. | |||
There was a problem hiding this comment.
seems unrelated to this PR? revert?
| # See the License for the specific language governing permissions and | ||
| # limitations under the License. | ||
|
|
||
| # Build portability tests with an updated submodule |
There was a problem hiding this comment.
this comment is now out of date
|
|
||
| cd "$(dirname "$0")"/../../.. | ||
|
|
||
| EXCEPTIONS=( |
There was a problem hiding this comment.
nit: rename to EXCLUDED_TARGETS or EXCLUDED_PATTERNS (as you wish)?
| @@ -0,0 +1,45 @@ | |||
| # Copyright 2021 The gRPC authors. | |||
There was a problem hiding this comment.
since you're adding this file, I think we need to cherrypick this PR into an import and see if this works internally as well.
| @@ -0,0 +1,26 @@ | |||
| # Copyright 2017 gRPC authors. | |||
There was a problem hiding this comment.
Generally I think we should avoid creating more kokoro jobs as these become hard to maintain, but for now I don't have a better alternative, so creating the 2 new kokoro jobs seems acceptable.
| ) | ||
|
|
||
|
|
||
| def bc_platform(**kwargs): |
There was a problem hiding this comment.
do you really need the bc_platform function?
In my PR this seemed to be the same case as create_rbe_exec_properties_dict
https://github.com/grpc/grpc/pull/25001/files#diff-e084337b59570d9fb8e3d40828b096dddf9056a9096eb32b44ceeb7fbb0383fcR33
| ) | ||
|
|
||
| for VERSION in "${SUPPORTED_VERSIONS[@]}"; do | ||
| ./test_single_bazel_version.sh "$VERSION" |
There was a problem hiding this comment.
nit: the output of 4 consecutive builds is going to be difficult to parse by humans.
Ideally these would be 4 independent "tasks".
There was a problem hiding this comment.
Should we instead add 4-5 tasks into distribtest_targets.py and save on needing to define 2 new kokoro jobs?
That would also make the output of the separate builds separated.
|
|
||
|
|
||
| export OVERRIDE_BAZEL_VERSION="$VERSION" | ||
| printf ' -%s' "${EXCEPTIONS[@]}" | xargs bazel build -- //... |
There was a problem hiding this comment.
this can be addressed later, but one thing this distribtest doesn't cover is depending upon grpc as a library in a simple "helloworld" project. Like this we will know that gRPC builds fine, but not whether it can be safely imported as a dependency.
|
This issue/PR has been automatically marked as stale because it has not had any update (including commits, comments, labels, milestones, etc) for 30 days. It will be closed automatically if no further update occurs in 7 day. Thank you for your contributions! |
|
This issue/PR has been automatically marked as stale because it has not had any update (including commits, comments, labels, milestones, etc) for 30 days. It will be closed automatically if no further update occurs in 7 day. Thank you for your contributions! |
|
Is this still blocked on the bazel toolchain update (same as in #25001). It would be good to address this somehow and unblock this functionality. This PR has been open for >6months now. |
|
I upgraded the repo to bazel 4.2.1, which makes many changes in this PR unnecessary: |
|
This needs to be rebased / updated now that #27486 has been merged. |
|
This issue/PR has been automatically marked as stale because it has not had any update (including commits, comments, labels, milestones, etc) for 30 days. It will be closed automatically if no further update occurs in 7 day. Thank you for your contributions! |
|
@gnossen let's revive this. |
|
This PR is very out of date and we might not need the compatibility layer for bazel 2.x anymore (since we support bazel 3.x,4.x and 5.x now), so I'm going to remove myself from the reviewer list. |
This PR adds Bazel Distribtests, officially codifying our supported range of Bazel versions. Two new CI jobs are added, whose triggers are TBD:
bazel buildon all supported Bazel versions, based on a manually curated list.Several targets are currently on a blocklist due to preexisting build failures. A next step is to triage this build errors and have them either fixed or removed.
One snag --
upbdoesn't currently support our range of builds. An older version of their repo supports the2.Xseries, while the commit I've introduced in this PR supports3+. I've added a check for the Bazel version and manually swap out theupbversion based on the Bazel version. This pattern should be moved to theupbrepo so it can support multiple Bazel versions and we can remove the check from our repo.