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 clean seems to be broken #39

Closed
tlemo opened this issue Mar 19, 2021 · 5 comments
Closed

bazel clean seems to be broken #39

tlemo opened this issue Mar 19, 2021 · 5 comments

Comments

@tlemo
Copy link
Contributor

tlemo commented Mar 19, 2021

bazel clean
WARNING: Blaze clean does not support starlark options. Ignoring options: [--@rules_cuda//cuda:cuda_targets=sm_60, --@rules_cuda//cuda:compiler=clang]
ERROR: Unrecognized arguments: --@rules_cuda//cuda:cuda_runtime=@tf_runtime//backends/gpu:cuda_stubs

Perhaps related to bazelbuild/bazel#11506 ?

@chsigg
Copy link
Collaborator

chsigg commented Apr 1, 2021

Yes, there is a bug in bazel. You can work around it with bazel --bazelrc=/dev/null clean --expunge

@tlemo
Copy link
Contributor Author

tlemo commented Apr 1, 2021

You can work around it with bazel --bazelrc=/dev/null clean --expunge

Thanks for the workaround. One small thing though, do you mean bazel --noworkspace_rc clean --expunge?
(--bazelrc=/dev/null is documented to ignore any following --bazelrc flags and as far as I can tell, it doesn't prevent the workspace .bazelrc from being used)

@chsigg
Copy link
Collaborator

chsigg commented Apr 1, 2021

You are absolutely right. I didn't test the workaround and wasn't aware of this difference between OSS bazel and Google-internal blaze.

@tlemo
Copy link
Contributor Author

tlemo commented Apr 1, 2021

No worries. After all, bazel itself still has plenty of leftover blaze references around :)

bazel clean
WARNING: Blaze clean ...

@chsigg
Copy link
Collaborator

chsigg commented Apr 3, 2021

bazel --noworkspace_rc clean --expunge is the right workaround until bazelbuild/bazel#11506 is fixed. Closing.

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