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] Error computing the main repository mapping: no such package '@@rules_kotlin//kotlin': #1211

Closed
sgowroji opened this issue Aug 28, 2024 · 1 comment · Fixed by #1183

Comments

@sgowroji
Copy link
Member

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4083#01919725-3854-45aa-958b-05bf8da50252

Platform: Ubuntu

Logs:

(04:02:03) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/2b7d31ca1d5c71319daa1407196088e9/external/release_archive/repository.bzl:54:17: An error occurred during the fetch of repository 'rules_kotlin':
   Traceback (most recent call last):
	File "/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/2b7d31ca1d5c71319daa1407196088e9/external/release_archive/repository.bzl", line 54, column 17, in archive_repository_implementation
		fail("local workspace %s does not exist" % workspace)
Error in fail: local workspace /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/2b7d31ca1d5c71319daa1407196088e9/external/rules_kotlin_head does not exist
(04:02:03) ERROR: Error computing the main repository mapping: no such package '@@rules_kotlin//kotlin': local workspace /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/2b7d31ca1d5c71319daa1407196088e9/external/rules_kotlin_head does not exist

Culprit:

Steps:

git clone https://github.com/bazelbuild/rules_kotlin
git reset e39c95265767de0a341360f7a28cdef8d40afc68  --hard
export USE_BAZEL_VERSION=5e77c5963e48ff0dadba38345f9c1c87e00d0667
bazel test //app:all 

CC Greenteam @mai93

@restingbull
Copy link
Collaborator

Fixed in #1183

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@sgowroji @restingbull and others