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

Build broken #230

Closed
schroederc opened this issue Jun 5, 2015 · 2 comments
Closed

Build broken #230

schroederc opened this issue Jun 5, 2015 · 2 comments

Comments

@schroederc
Copy link
Contributor

$ bazel build //src:bazel
ERROR: <redacted>/bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar',  but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: <redacted>/bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar',  but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: <redacted>/bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar',  but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: <redacted>/bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar',  but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: <redacted>/bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar',  but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: <redacted>/bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar',  but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
WARNING: errors encountered while analyzing target '//src:bazel': it will not be built.
INFO: Found 0 targets...
ERROR: execution phase succeeded, but there were loading phase errors.
INFO: Elapsed time: 0.241s, Critical Path: 0.00s
@damienmg
Copy link
Contributor

damienmg commented Jun 5, 2015

You need to rebuild bazel with compile.sh. We should not expect more of
those kind of change in the future.
Le ven. 5 juin 2015 à 18:44, Cody Schroeder notifications@github.com a
écrit :

$ bazel build //src:bazel
ERROR: /bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar', but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: /bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar', but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: /bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar', but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: /bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar', but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: /bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar', but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: /bazel/tools/build_rules/genproto.bzl:60:3: every rule of type gensrcjar implicitly depends upon the target '//external:jar', but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
WARNING: errors encountered while analyzing target '//src:bazel': it will not be built.
INFO: Found 0 targets...
ERROR: execution phase succeeded, but there were loading phase errors.
INFO: Elapsed time: 0.241s, Critical Path: 0.00s


Reply to this email directly or view it on GitHub
#230.

Damien

@schroederc
Copy link
Contributor Author

A newer version does fix it.

keertk pushed a commit that referenced this issue Aug 13, 2024
#23290)

…69)"

This reverts commit ffe1df5.

Causes race conditions, see #23288 for details.

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

No branches or pull requests

2 participants