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] No repository visible as '@android_studio_2023_1' from main repository with Bazel@HEAD #6680

Closed
sgowroji opened this issue Aug 29, 2024 · 9 comments
Assignees
Labels

Comments

@sgowroji
Copy link
Member

sgowroji commented Aug 29, 2024

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4087#01919c53-4f61-459b-9d5d-440eb41ecd70

Platform: Ubuntu

Logs:

(04:10:41) ERROR: no such package '@@[unknown repo 'android_studio_2023_1' requested from @@]//': The repository '@@[unknown repo 'android_studio_2023_1' requested from @@]' could not be resolved: No repository visible as '@android_studio_2023_1' from main repository
(04:10:41) ERROR: /var/lib/buildkite-agent/builds/bk-docker-1lm9/bazel-org-repo-root/intellij/intellij_platform_sdk/BUILD:1125:10: no such package '@@[unknown repo 'android_studio_2023_1' requested from @@]//': The repository '@@[unknown repo 'android_studio_2023_1' requested from @@]' could not be resolved: No repository visible as '@android_studio_2023_1' from main repository and referenced by '//intellij_platform_sdk:application_info_json'
(04:10:41) ERROR: Analysis of target '//aswb:normal_integration_tests_api_version' failed; build aborted: Analysis failed
(04:10:41) INFO: Elapsed time: 1.694s, Critical Path: 0.07s
(04:10:41) INFO: 5 processes: 5 internal.
(04:10:41) ERROR: Build did NOT complete successfully
(04:10:41) FAILED:

Culprit: bazelbuild/bazel@5881c38

Steps:

 git clone https://github.com/bazelbuild/intellij
git reset a510e66ce2b8ba468c144f2b13c564dbeb294ae6  --hard
export USE_BAZEL_VERSION=00f45195f34bf31b021c6a9568189f4f871ad6ff
bazel build //aswb/... 

CC Greenteam @mai93

@sgowroji
Copy link
Member Author

bazel --nosystem_rc --nohome_rc info
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.IllegalStateException: java.lang.RuntimeException: Unrecoverable error while evaluating node 'PlatformMappingValue.Key{path=platform_mappings, wasExplicitlySetByUser=false}' (requested by nodes 'BuildConfigurationKeyValue.Key{buildOptions=10a2664ab920803a5609c68f17a5d3320fbcbd70c7c12a0fdd8ee360e5f677b1}')
	at com.google.devtools.build.lib.skyframe.SkyframeExecutor.evaluateSkyKeys(SkyframeExecutor.java:2026)
	at com.google.devtools.build.lib.skyframe.SkyframeExecutor.evaluateSkyKeys(SkyframeExecutor.java:2002)
	at com.google.devtools.build.lib.skyframe.SkyframeExecutor.createBuildConfigurationKey(SkyframeExecutor.java:1958)
	at com.google.devtools.build.lib.skyframe.SkyframeExecutor.getConfiguration(SkyframeExecutor.java:1882)
	at com.google.devtools.build.lib.runtime.commands.InfoCommand.lambda$exec$0(InfoCommand.java:158)
	at com.google.common.base.Suppliers$NonSerializableMemoizingSupplier.get(Suppliers.java:181)
	at com.google.devtools.build.lib.runtime.commands.InfoCommand.exec(InfoCommand.java:219)
	at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.execExclusively(BlazeCommandDispatcher.java:679)
	at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.exec(BlazeCommandDispatcher.java:252)
	at com.google.devtools.build.lib.server.GrpcServerImpl.executeCommand(GrpcServerImpl.java:607)
	at com.google.devtools.build.lib.server.GrpcServerImpl.lambda$run$1(GrpcServerImpl.java:676)
	at io.grpc.Context$1.run(Context.java:566)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: Unrecoverable error while evaluating node 'PlatformMappingValue.Key{path=platform_mappings, wasExplicitlySetByUser=false}' (requested by nodes 'BuildConfigurationKeyValue.Key{buildOptions=10a2664ab920803a5609c68f17a5d3320fbcbd70c7c12a0fdd8ee360e5f677b1}')
	at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:547)
	at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:435)
	at java.base/java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
Caused by: java.lang.NullPointerException: Null repoMapping
	at com.google.devtools.build.lib.cmdline.AutoValue_Label_RepoContextImpl.<init>(AutoValue_Label_RepoContextImpl.java:20)
	at com.google.devtools.build.lib.cmdline.Label$RepoContext.of(Label.java:122)
	at com.google.devtools.build.lib.skyframe.config.PlatformMappingFunction.compute(PlatformMappingFunction.java:82)
	at com.google.devtools.build.lib.skyframe.config.PlatformMappingFunction.compute(PlatformMappingFunction.java:60)
	at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:467)
	... 7 more

@tpasternak
Copy link
Collaborator

🤔 I'm not sure if we can fix it on our side

@sgowroji
Copy link
Member Author

Hi @tpasternak , Above failures are related to Bazel downstream CI,  And @meteorcloudy is working on it.

@tpasternak
Copy link
Collaborator

Thanks!

@meteorcloudy
Copy link
Member

This is due to bazelbuild/bazel#23023. After --enable_workspace is flipped to false, users have to explicitly specify it where it's needed, or fully migrate to Bzlmod.

@mai93
Copy link
Collaborator

mai93 commented Aug 30, 2024

We have bzlmod enabled in the master branch, example failure where --enable_bzlmod is used. From the build output:

(04:23:33) INFO: Reading rc options for 'build' from /var/lib/buildkite-agent/builds/bk-docker-vspt/bazel-org-repo-root/intellij/.bazelrc:
--
  | Inherited 'common' options: --enable_bzlmod

@mai93
Copy link
Collaborator

mai93 commented Sep 4, 2024

I think we still need to add --enable_workspace even though we have --enable_bzlmod because we have some dependencies brought in from WORKSPACE.bzlmod. I moved some http_archive to MODULE.bazel in (#6724). The remaining in WORKSPACE.bzlmod is rules_scala

@agluszak
Copy link
Collaborator

agluszak commented Sep 4, 2024

rules_scala, the usual suspect :)

@mai93 mai93 closed this as completed Sep 9, 2024
@mai93 mai93 removed the awaiting-maintainer Awaiting review from Bazel team on issues label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants