-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
WIP: disable WORKSPACE in shell integration tests #23087
WIP: disable WORKSPACE in shell integration tests #23087
Conversation
All of the native Android rule tests require WORKSPACE to exist, so I think CI won't pass until we delete those tests and eventually the rules. |
Do you still want to keep the android tests in Bazel repo? (We disabled them on macOS already) If so, we can still set |
I don't think we've migrated all of these tests to rules_android yet, so we can't outright delete them for now. I'd be OK with disabling them for Linux and Windows to unblock this work. |
Got it, then I'll just enable WORKSPACE for those tests to keep them running. |
f1e76db
to
533d3a7
Compare
c59347b
to
722a3f9
Compare
- Added functions for setting up common dependencies in MODULE.bazel - Use a shorter bazel_root on Windows - Added setup_module_dot_bazel to replace write_default_lockfile eventually - Removed TEST_REPOSITORY_HOME support A part of #23087 Working towards: #23023 PiperOrigin-RevId: 660748611 Change-Id: I55193953b429c18414ec092f567c98af36d7c34a
This PR has been broken down and merged. |
Working towards #23023
This PR is huge, I'm going to try to break it down: