The GitHub Actions job "Run Integration Tests" on rocketmq.git/feat/rip2-proxy-admin has failed. Run started by GitHub user zhaohai666 (triggered by zhaohai666).
Head commit for run: 3146aa74cfb090fa33bf73a995a3015b79d53ccc / zhaohaihzb <[email protected]> build(rip2): generate proto from the rocketmq-apis submodule in the Bazel build The Bazel build resolved org.apache.rocketmq:rocketmq-proto from Maven Central, which has no artifact containing the RIP-2 admin contract (admin.proto), so //proxy:proxy could not see the admin types. Generate the protocol classes from the submodule instead, mirroring what the rocketmq-proto Maven module does. The submodule's own BUILD files pull in toolchains this workspace does not declare (graknlabs_bazel_distribution, googleapis), so the directory stays in .bazelignore and is surfaced as @rocketmq_apis via new_local_repository and a minimal build file. That keeps 'bazel build //...' from trying to build it. protoc and protoc-gen-grpc-java are fetched as prebuilt executables with http_file: rules_jvm_external can only resolve jar artifacts, and the grpc-java Bazel toolchain would build both from C++ sources. The well-known type protos come from the protobuf source archive, because the standalone protoc does not bundle them; their include dir must be on the protoc import path or definition.proto fails and every symbol it defines looks undefined. proxy, auth and test now depend on //rocketmq-proto:rocketmq-proto instead of @maven//:org_apache_rocketmq_rocketmq_proto. Report URL: https://github.com/apache/rocketmq/actions/runs/34189722510 With regards, GitHub Actions via GitBox
