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

[Bazel CI] Bazel@HEAD failed to build Bazel itself in downstream #21864

Closed
sgowroji opened this issue Apr 1, 2024 · 2 comments
Closed

[Bazel CI] Bazel@HEAD failed to build Bazel itself in downstream #21864

sgowroji opened this issue Apr 1, 2024 · 2 comments
Assignees
Labels
breakage P1 I'll work on this now. (Assignee required) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: bug

Comments

@sgowroji
Copy link
Member

sgowroji commented Apr 1, 2024

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3765#018e97d5-1a26-4f83-9b08-3570811e9ea6

Platform: MacOS

Logs:

ERROR: An error occurred during the fetch of repository '_main~bazel_build_deps~bootstrap_repo_cache':
   Traceback (most recent call last):
	File "/Users/buildkite/builds/bk-imacpro-5/bazel-org-repo-root/bazel/distdir.bzl", line 89, column 42, in _repo_cache_tar_impl
		http_artifacts = parse_http_artifacts(ctx, lockfile_path, ctx.attr.repos)
	File "/Users/buildkite/builds/bk-imacpro-5/bazel-org-repo-root/bazel/src/tools/bzlmod/utils.bzl", line 108, column 13, in parse_http_artifacts
		fail("Could not find all required repos, missing: %s" % missing_repos)
Error in fail: Could not find all required repos, missing: ["grpc~~grpc_repo_deps_ext~bazel_gazelle", "grpc~~grpc_repo_deps_ext~bazel_skylib", "grpc~~grpc_repo_deps_ext~com_envoyproxy_protoc_gen_validate", "grpc~~grpc_repo_deps_ext~com_github_cncf_udpa", "grpc~~grpc_repo_deps_ext~com_google_googleapis", "grpc~~grpc_repo_deps_ext~envoy_api", "grpc~~grpc_repo_deps_ext~rules_cc", "rules_kotlin~~rules_kotlin_extensions~com_github_jetbrains_kotlin"]

Culprit:

Steps:

git clone https://github.com/bazelbuild/bazel
git reset 753dc9750714af581147f6aa338adeb07a9dcb57  --hard
export USE_BAZEL_VERSION=753dc9750714af581147f6aa338adeb07a9dcb57
bazel test - //scripts/... //src/main/starlark/tests/builtins_bzl/... //src/test/... //src/tools/execlog/... //src/tools/singlejar/... //src/tools/workspacelog/... //third_party/ijar/... //tools/android/... //tools/aquery_differ/... //tools/python/... //tools/bash/... -//src/test/shell/bazel:starlark_repository_test -//src/test/shell/bazel/apple:bazel_apple_test -//src/test/shell/bazel/apple:bazel_objc_test -//src/test/java/com/google/devtools/build/lib/platform:SystemMemoryPressureEventTest -//src/test/shell/bazel:bazel_determinism_test -//src/test/shell/bazel:jdeps_test -//src/test/shell/bazel:srcs_test -//src/test/shell/bazel/android:android_instrumentation_test_integration_test -//src/test/shell/bazel/android:android_instrumentation_test_integration_test_with_head_android_tools -//src/test/shell/bazel/android:aapt_integration_test -//src/test/shell/bazel/android:aapt_integration_test_with_head_android_tools 

CC Greenteam @fweikert

@sgowroji sgowroji added type: bug breakage untriaged team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website labels Apr 1, 2024
@meteorcloudy meteorcloudy self-assigned this Apr 16, 2024
@meteorcloudy meteorcloudy added P1 I'll work on this now. (Assignee required) and removed untriaged labels Apr 16, 2024
@meteorcloudy
Copy link
Member

meteorcloudy commented Apr 16, 2024

This was likely caused by 87b53ab, we need to bring back bazelbuild/continuous-integration#1878 (reverted in bazelbuild/continuous-integration#1925) to resolve this.

Wyverald pushed a commit to bazelbuild/continuous-integration that referenced this issue Apr 16, 2024
Re-applying
#1878 to
address
bazelbuild/bazel#21864 (comment)

The postsubmit.yml was synced to the latest version in Bazel
@meteorcloudy meteorcloudy changed the title [Bazel CI] Bazel fetch fails with FileNotFoundException on Bazel@HEAD [Bazel CI] Bazel@HEAD failed to build Bazel itself in downstream Apr 16, 2024
@meteorcloudy
Copy link
Member

Bazel is now green at https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3797

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breakage P1 I'll work on this now. (Assignee required) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: bug
Projects
None yet
Development

No branches or pull requests

2 participants