| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
subclassed by a skylark-specific implementation
RELNOTES: None.
PiperOrigin-RevId: 174486116
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 174485947
|
|
|
|
| |
PiperOrigin-RevId: 174482602
|
|
|
|
| |
PiperOrigin-RevId: 174481563
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 174479316
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Whether a resource is accepted or rejected by density-based resource filtering
is dependent on what other resources are available. When filtering resources in
execution, this was taken into account - resources were filtered after merging.
To replicate this behavior when filtering in analysis, we must look at both
local and transitive resources before we actually filter anything.
This process makes filtering with dynamic configuration extremely inefficient, since the NestedSet of transitive resources must be collapsed at each library target. We can fix this by only looking at the transitive resources at the top-level target, even when using dynamic filtering. I'm not implementing that in this change, however, since dynamic filtering is relatively low priority and this review is already pretty big.
Note that some of the messiness around filtering ResourceDependencies and
NestedSet<ResourceContainer> will go away once those NestedSets are removed.
Also, stop filtering resources in android_test, since android_test can never specify resource filters.
RELNOTES: none
PiperOrigin-RevId: 174474491
|
|
|
|
| |
PiperOrigin-RevId: 174473387
|
|
|
|
|
|
|
|
|
|
| |
Small cleanup to avoid saving a set of the LTOBackendArtifact objects on the
CppLinkAction. They can be accessed from the CppLinkActionBuilder, and
keeping them on the CppLinkAction prevents them from being GC'ed when
the builder is destroyed.
RELNOTES: None
PiperOrigin-RevId: 174469228
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using `bazel build //site` will now build the site (needs the proper
version of Jekyll in the path :/), `bazel run //site` will serve it
using Jekyll.
This change also contains the yaml file to build and deploy the
site on Google Cloud Container Builder. This will allow to remove
that special hook from our CI.
Note: this is copied from https://github.com/bazelbuild/bazel-blog
Change-Id: I6bb04fea0fa80623bd5d25a5f191ae49e8074e92
PiperOrigin-RevId: 174459256
|
|
|
|
|
|
| |
This is no longer maintained and the CI is turned down.
PiperOrigin-RevId: 174456265
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In addition to the $(location) function, we now also support $(rootpath) and
$(execpath) functions.
Unfortunately, we have to do this in two places since the Skylark API for expand_location has to continue calling into LocationExpander in order to preserve its semantic contract.
Progress on #2475.
RELNOTES[NEW]:
In addition to $(location), Bazel now also supports $(rootpath) to obtain
the root-relative path (i.e., for runfiles locations), and $(execpath) to
obtain the exec path (i.e., for build-time locations)
PiperOrigin-RevId: 174454119
|
|
|
|
| |
PiperOrigin-RevId: 174403764
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 174397203
|
|
|
|
| |
PiperOrigin-RevId: 174388297
|
|
|
|
|
|
|
| |
"blaze test".
RELNOTES: None.
PiperOrigin-RevId: 174386473
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward again without the changes to expand_location, but with the trimming fix from https://github.com/bazelbuild/bazel/commit/19617360121635a77ffec99b84d825e7d9b260b1.
*** Original change description ***
Automated rollback of commit ca77f608e486bf7aa762565d25bf7b9e30f2268c.
This also rolls back unknown commit.
*** Reason for rollback ***
Affected expand_location Skylark API semantics - it no longer accepts ${abc} or plain dollar signs, but complains.
*** Original change description ***
Extend TemplateExpander to handle $(func param) expansion
Rewrite the Expander to use the new functionality; also rewrite the Skylark
expand_location function to use it.
PiperOrigin-RevId: 174384095
|
|
|
|
|
|
| |
Closes #4009.
PiperOrigin-RevId: 174380096
|
|
|
|
|
|
|
| |
This includes docs on how to use the memory profiler.
RELNOTES: None
PiperOrigin-RevId: 174374064
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks alphago targets.
*** Original change description ***
Remove CppConfiguration#getFeatures in favor of
CcToolchainProvider#getFeatures.
PiperOrigin-RevId: 174373331
|
|
|
|
|
|
|
|
|
|
| |
Previously, linkstamp objects would be built without -fPIC. When linked
into a PIE binary, this leads to text relocations, which causes IFUNC
resolution to segfault (the resolution function is called while the
binary is mapped RW).
RELNOTES: None.
PiperOrigin-RevId: 174366114
|
|
|
|
|
|
|
| |
OptionsParserTest are implemented in ParamsFilePreProcessorTest, ShellQuotedParamsFilePreProcessorTest and UnquotedParamsFilePreProcessorTest.
RELNOTES: None.
PiperOrigin-RevId: 174359569
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 174355404
|
|
|
|
| |
PiperOrigin-RevId: 174354036
|
|
|
|
|
|
|
| |
Since the problem or the means to fix it is usually on the user side.
RELNOTES=none
PiperOrigin-RevId: 174348233
|
|
|
|
| |
PiperOrigin-RevId: 174343502
|
|
|
|
|
|
|
| |
Make sure that multiple calls to parse() follow each other sequentially. This is necessary for blazerc expansion, which occurs first in command order, then blazerc order.
RELNOTES: None.
PiperOrigin-RevId: 174343241
|
|
|
|
|
|
|
|
| |
This allows Skylib `skylark_library` users to use `hash.bzl` as a file dependency without the base Bazel rules having to import the actual `skylark_library` rule from Skylib.
Closes #4000.
PiperOrigin-RevId: 174337147
|
|
|
|
| |
PiperOrigin-RevId: 174333380
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 174330237
|
|
|
|
|
|
|
|
|
|
|
| |
- Migrate bazel-tests-remote.json file from
bazelbuild/continuous-integration repo to bazelbuild/bazel repo.
- Update toolchain and configs to use container v0.2.0 and new
configs (v0.7.0 for c++, v0.6.0 for java).
Change-Id: Ib376f662c6c6cec617d82133254f9a12ef67e748
PiperOrigin-RevId: 174329569
|
|
|
|
| |
Change-Id: If1b3b84e8e507999a92548d9274b8233701e06cb
|
|
|
|
|
|
|
| |
quotes
RELNOTES: None
PiperOrigin-RevId: 174319420
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 174318660
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 174310059
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 174307524
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 174305935
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 174305030
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 174229364
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 174219672
|
|
|
|
| |
PiperOrigin-RevId: 174202685
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 174199997
|
|
|
|
|
|
| |
When --define EXECUTOR=remote is specified in bazel command, embedded tool singlejar and ijar will be compiled remotely from source.
PiperOrigin-RevId: 174195094
|
|
|
|
|
|
|
| |
This omits validation for this transition, which will follow in a future change.
RELNOTES: None.
PiperOrigin-RevId: 174183651
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Blaze nightly
Example failing test: []
*** Original change description ***
Allow android_test to properly inherit resources
RELNOTES: none
PiperOrigin-RevId: 174182803
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 174124176
|
|
|
|
|
|
|
|
| |
multiple shards. Also fix some weirdnesses with how shard assignments were recorded.
RELNOTES: None.
PiperOrigin-RevId: 174095450
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/issues/903
RELNOTES: None
PiperOrigin-RevId: 174079202
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 174062560
|
|
|
|
|
|
|
|
|
|
|
| |
In the next review, to handle issues around density filtering, ResourceFilterFactory will return another object that actually handles filtering. To ensure stuff is named properly, rename ResourceFilter to ResourceFilterFactory now so that the new class can be called ResourceFilter.
This is a straightforward automated refactor, followed with some automated reformatting to make linting happy.
I used the name ResourceFilterFactory, rather than the more concise ResourceFilters, as this class actually contains state (both around what filtering should currently do and about what resources were filtered out) and isn't just a helper class.
RELNOTES: none
PiperOrigin-RevId: 174049618
|
|
|
|
|
|
|
|
|
| |
ParallelSkyQueryUtils.RBuildFilesVisitor. Also a minor tweak of the batch size for feeding results to the callback.
Also correctly use the packageSemaphore in SkyQueryEnvironment's non-parallel implementation of rbuildfiles.
RELNOTES: None
PiperOrigin-RevId: 174039067
|