[Bazel CI] ERROR: While resolving toolchains for target invalid registered toolchain '@local_jdk//:runtime_toolchain_definition': error loading package repo 'local_config_platform'
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- build-system, ci-cd
Research direction
Start with the linked Buildkite run and the target in configurations/cc_binary_selectable_copts/BUILD, especially app_with_feature1_native_binary. Compare the Windows and Ubuntu failures and trace the invalid local_jdk toolchain and local_config_platform repository error. Done means the affected CI builds complete without the toolchain-resolution failure.
Written by the indexing model from the issue text.
Description
CI: https://buildkite.com/bazel/bazel-bazel-examples/builds/4897#019ab860-fcd1-4a24-9b97-56f4f228991f
Platform: Windows, Ubuntu
Logs:
(00:20:12) ERROR: /workdir/configurations/cc_binary_selectable_copts/BUILD:9:10: While resolving toolchains for target //cc_binary_selectable_copts:app_with_feature1_native_binary (9d6e610): invalid registered toolchain '@local_jdk//:runtime_toolchain_definition': error loading package '@@rules_java++toolchains+local_jdk//': Unable to find package for @@[unknown repo 'local_config_platform' requested from @@rules_java++toolchains+local_jdk]//:constraints.bzl: The repository '@@[unknown repo 'local_config_platform' requested from @@rules_java++toolchains+local_jdk]' could not be resolved: No repository visible as '@local_config_platform' from repository '@@rules_java++toolchains+local_jdk'.
(00:20:12) ERROR: Analysis of target '//cc_binary_selectable_copts:app_with_feature1' failed; build aborted: Analysis failed
(00:20:12) INFO: Elapsed time: 1.387s, Critical Path: 0.05s
(00:20:12) INFO: 1 process: 1 internal.
(00:20:12) ERROR: Build did NOT complete successfully
CC Greenteam @Wyverald
- Dominant language
- Starlark
- Stars
- 957
- Forks
- 578
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bazelbuild/examples
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
bazelbuild/examples#706 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
bazelbuild/examples#650 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
bazelbuild/examples#641 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
bazelbuild/examples#634 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bazelbuild/examples#627 ·
All issues in bazelbuild/examples
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
agentic-workflows cascade-suspected
Difficulty 1/5 Under an hour Newbie friendliness 88/100