You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[5.1] Adding Starlark dependencies to the package //external (bazelbuild#14991)
* Adding Starlark dependencies to the package //external
This is an alternative approach to fixbazelbuild#14280. It adds transitive closure of Starlark dependencies to `//external` package when loading `WORKSPACE` file, so it can be processed in the same way as `BUILD` files during query execution. Comparing to the approach taken in bazelbuild#14497, this approach is less intrusive, but not able to distinguish the extension files needed by `//external:foo` and `//external:bar`, meaning `buildfiles(//external:foo)` returns the same result as `buildfiles(//external:*)`. However, this behavior is consistent with other packages. For example, `buildfiles(//foo:bar)` has the same result as `buildfiles(//foo:*)`.
Closesbazelbuild#14630.
PiperOrigin-RevId: 424092916
(cherry picked from commit a6c3f23)
* Avoid bazel_module_test timeout on macos
https://buildkite.com/bazel/bazel-bazel/builds/17785#9a1fb564-c6f9-4e69-ac8f-87c422a002b0
By setting the test size to "large".
RELNOTES:None
PiperOrigin-RevId: 409114345
(cherry picked from commit 1d99391)
Co-authored-by: Zhongpeng Lin <[email protected]>
Co-authored-by: pcloudy <[email protected]>
0 commit comments