| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 185879731
|
|
|
|
|
|
|
|
| |
a strict win:
There are only two places Canonicalizer did PathFragment interning: PackageIdentifier creation and Package creation. PackageIdentifiers are always interned by a separate interner, and so the underlying PathFragment will be in 1-1 correspondence with PackageIdentifiers (per repo). Moreover, Packages are created with a PackageIdentifier already existing, so it will use the same PathFragment of the unique PackageIdentifier.
PiperOrigin-RevId: 185877942
|
|
|
|
|
|
|
| |
We call Map#put in Map#computeIfAbsent. No idea how this ever worked.
RELNOTES: None
PiperOrigin-RevId: 185876437
|
|
|
|
|
|
|
|
| |
android desugaring
RELNOTES: None.
PiperOrigin-RevId: 185863194
|
|
|
|
|
|
|
|
| |
The BVTC is primarily intended for analysis tests, and those should not have
access to BinTools. However, there are a few subclasses that misuse it for
integration tests, and those need to create their own BinTools instances now.
PiperOrigin-RevId: 185862672
|
|
|
|
|
|
| |
mechanism as for normal actions, have the ActionTemplateExpansionFunction look the template up when needed.
PiperOrigin-RevId: 185861672
|
|
|
|
|
|
| |
exported by cc_library.
PiperOrigin-RevId: 185852115
|
|
|
|
| |
PiperOrigin-RevId: 185850685
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 185847904
|
|
|
|
| |
PiperOrigin-RevId: 185847377
|
|
|
|
| |
PiperOrigin-RevId: 185844072
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 185838543
|
|
|
|
|
|
|
|
| |
calculation, so we don't have to have the whole package.
Memory increase should be minimal because there aren't that many environment groups, but it's further minimized by breaking an inner class UnpackagedEnvironmentGroup out of EnvironmentGroup. Previously, each EnvironmentGroup cost 40 bytes (24 bytes for first three fields, 8 for next two, 8 for last field because of alignment). Each UnpackagedEnvironmentGroup costs 32 bytes (4 fields), while the EnvironmentGroup now costs 24 bytes. So a loss of 16 bytes per EnvironmentGroup: shouldn't be noticeable.
PiperOrigin-RevId: 185837140
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add "JAVA_RUNFILES" (and "RUNFILES_DIR") to the
dict that Runfiles.EnvVars() returns in the Python
runfiles library, so Python programs that use the
Python runfiles library in @bazel_tools can now
run java_binary data-dependencies as subprocesses
and the latter will find the runfiles.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I0566f6d3c68631a1d99e67964fbe8019ee82324b
PiperOrigin-RevId: 185812948
|
|
|
|
|
|
|
|
|
| |
This fixes #3201 by preventing tests that haven't actually run to be written to the test.xml. This is consistent with how e.g. surefire reports work, tests that were filtered out do not appear in the xml.
This allows changing the Bazel plugin in such a way that does not depend on `time` being 0.0.
Closes #4596.
PiperOrigin-RevId: 185810400
|
|
|
|
|
|
|
| |
The logic is split between CcCompilationHelper and CcLinkingHelper.
RELNOTES:none
PiperOrigin-RevId: 185809915
|
|
|
|
|
|
|
| |
It's never used during analysis, it shouldn't be used during analysis, so let's
not make it available during analysis.
PiperOrigin-RevId: 185808384
|
|
|
|
|
|
|
| |
RunfilesSupport.owningExecutable can clearly never be null because the first thing the constructor does is reject it if it's null.
Change-Id: Ie861d96a2a2ab6937f1e27a6745cf1cb2f50e0fb
PiperOrigin-RevId: 185806352
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Remove example changes; those need to build with the last Bazel release.
*** Original change description ***
Automated rollback of commit 0f9c6ea574918dda094cf5423fa3822112846c30.
*** Reason for rollback ***
Breaks Kokoro and I accidentally submitted the change without presubmit checks.
*** Original change description ***
Make __init__.py files creation optional
Introduce a new attribute to py_binary and py_test to control whether to
create `__init__.py` or not.
Fixes https://github.com/bazelbuild/rules_python/issues/55
Closes #4470.
PiperOrigin-RevId: 185806241
|
|
|
|
| |
PiperOrigin-RevId: 185770217
|
|
|
|
|
|
| |
ConfiguredTargetKeys that own the PlatformInfo.
PiperOrigin-RevId: 185770105
|
|
|
|
|
|
|
|
| |
JavaBuilder and friends will write this into the manifest of the produced jars to assist with add_dep commands, when strict_deps is violated.
This will obviate the need for blaze to pass jar owners on the command line.
PiperOrigin-RevId: 185763422
|
|
|
|
|
|
|
| |
can also be called by getInputFilesForExtraAction rather than duplicating the logic.
RELNOTES: None
PiperOrigin-RevId: 185757663
|
|
|
|
|
|
|
|
|
| |
CodecScanner.
Introduces a class, CodecRegisterer, to allow customization of the scan-based
registration process.
PiperOrigin-RevId: 185749655
|
|
|
|
|
|
| |
classpath heuristic
PiperOrigin-RevId: 185746460
|
|
|
|
|
|
| |
The real blocker is PlatformInfo, which is coming.
PiperOrigin-RevId: 185742130
|
|
|
|
|
|
| |
are needed, so just use that.
PiperOrigin-RevId: 185738140
|
|
|
|
| |
PiperOrigin-RevId: 185735582
|
|
|
|
| |
PiperOrigin-RevId: 185733313
|
|
|
|
|
|
| |
by cc_library.
PiperOrigin-RevId: 185729248
|
|
|
|
| |
PiperOrigin-RevId: 185728950
|
|
|
|
| |
PiperOrigin-RevId: 185728682
|
|
|
|
|
|
| |
Roll forward of unknown commit
PiperOrigin-RevId: 185727344
|
|
|
|
|
| |
Change-Id: I636d98fdee72c1cae7547f1dc26f78fe4b3e0bb3
PiperOrigin-RevId: 185723619
|
|
|
|
|
|
| |
just as well as the target.
PiperOrigin-RevId: 185721605
|
|
|
|
|
|
|
| |
This avoids iterator, string builder, and string garbage.
RELNOTES: None
PiperOrigin-RevId: 185703066
|
|
|
|
|
|
|
| |
statistics tests.
RELNOTES: None.
PiperOrigin-RevId: 185700811
|
|
|
|
| |
PiperOrigin-RevId: 185694489
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Kokoro and I accidentally submitted the change without presubmit checks.
*** Original change description ***
Make __init__.py files creation optional
Introduce a new attribute to py_binary and py_test to control whether to
create `__init__.py` or not.
Fixes https://github.com/bazelbuild/rules_python/issues/55
Closes #4470.
PiperOrigin-RevId: 185676592
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce a new attribute to py_binary and py_test to control whether to
create `__init__.py` or not.
Fixes https://github.com/bazelbuild/rules_python/issues/55
Closes #4470.
PiperOrigin-RevId: 185672243
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Windows native {java,py,sh}_binary launcher
now picks up the RUNFILES_MANIFEST_FILE and
RUNFILES_DIR envvars from the environment. This
enables running such binaries even when they are
data-dependencies of other binaries and thus have
no runfiles (manifest or directory) of their own.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I1bc8e30f81b9932ea7c96ded2717ac9d0600403d
PiperOrigin-RevId: 185656004
|
|
|
|
|
|
|
|
|
|
| |
We can now compile
//src/tools/singlejar:token_stream on Windows.
See https://github.com/bazelbuild/bazel/issues/2241
Change-Id: I98f86e608e5ebaf685e4de26b2dabe75fcca78d2
PiperOrigin-RevId: 185655986
|
|
|
|
|
|
|
| |
Fixes MSVC C4311 pointer truncation warning.
Change-Id: Ic64168d620db010717189200c37c419cccac0653
PiperOrigin-RevId: 185653953
|
|
|
|
|
| |
Change-Id: Icbc478f87d622665b16c13c76518087ac089899e
PiperOrigin-RevId: 185645880
|
|
|
|
|
| |
Change-Id: Ib0c957de68a8a8035f2e13d7c9fe8d1549a3744d
PiperOrigin-RevId: 185645675
|
|
|
|
| |
PiperOrigin-RevId: 185624059
|
|
|
|
| |
PiperOrigin-RevId: 185609826
|
|
|
|
|
|
|
|
| |
concrete subclasses. Improve debugging message on serialization failures.
Lot of test-side changes to make sure aspects are properly registered with the RuleClassProvider.
PiperOrigin-RevId: 185607202
|
|
|
|
|
|
|
| |
Cleaning up references to {Des,S}erializationContext.UNTHREADED_PLEASE_REMOVE,
deleting the code is easier than deciding how to adapt context.
PiperOrigin-RevId: 185602054
|
|
|
|
|
|
| |
based on feature configuration
PiperOrigin-RevId: 185600940
|