| Commit message (Collapse) | Author | Age |
|
|
|
| |
Change-Id: Ie8b7dfe207f05f69fdd4499c38cb8baefa3d997f
|
|
|
|
|
|
|
| |
Previously, only arguments in parameter file are converted to long path.
Now, we convert every path we use to long path.
Change-Id: Iafff8b7a0f69f82cc9f8f9399b35528814eb7715
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
aar_resources_extractor now supports long paths
on Windows.
If the script needs to extract a file from the
AAR where the destination path is too long, the
script will:
1. create a temporary junction under a short path,
pointing to the destination directory (which
has a long path)
2. extract the file under the junction
3. delete the junction and the temp directory
See https://github.com/bazelbuild/bazel/issues/3659
Change-Id: Ie85665b360a6514afaac546aaec8869224fe9d06
PiperOrigin-RevId: 167545085
|
|
|
|
| |
PiperOrigin-RevId: 167520688
|
|
|
|
|
|
|
| |
This removes our dependency on third_party/joda_time, which can be removed in the next commit.
Change-Id: Ibda131d34d0abdc2d675db4bfbd2e99480c055ee
PiperOrigin-RevId: 167515260
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167505493
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167502103
|
|
|
|
|
|
|
|
|
| |
host JAVA/JAVABASE attributes.
Also fix a few lint warnings and move a class so that it's closer to where it's actually used.
RELNOTES: None.
PiperOrigin-RevId: 167501208
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167501207
|
|
|
|
|
|
|
| |
Mutiple other cleanups in the parser, update code documentation.
RELNOTES: None.
PiperOrigin-RevId: 167501136
|
|
|
|
|
|
|
|
| |
BUILD files.
Replace all ":relative" labels with "//absolute:path" labels for easier search & replace.
PiperOrigin-RevId: 167500985
|
|
|
|
|
| |
Change-Id: I3bd594f538d81c7321e7a3c61175beb76cf326b2
PiperOrigin-RevId: 167499849
|
|
|
|
|
|
|
|
|
| |
The only case this exception is thrown is when there is
a bug in Bazel and we should surface the whole stacktrace.
See #3664
PiperOrigin-RevId: 167492638
|
|
|
|
|
|
|
| |
RELNOTES[INC]:
Integer overflow (on signed 32 bit numbers) in BUILD/bzl files is an error.
PiperOrigin-RevId: 167486707
|
|
|
|
|
| |
Change-Id: I3fce66ec2e63d152aafc0cf9ea067d6dbf1245f7
PiperOrigin-RevId: 167484075
|
|
|
|
| |
PiperOrigin-RevId: 167480127
|
|
|
|
| |
PiperOrigin-RevId: 167477112
|
|
|
|
|
|
|
|
|
|
| |
COMPILER_MSVC is really a misnomer. It really means "use native Win32
APIs instead of Unix emulation (msys)". Since we no longer develop
msys-based version, we should remove all #if (windows && !COMPILER_MSVC)
sections from the code base.
Change-Id: Ibf0f62e4077027b799885c5dcbbce2da626b281c
PiperOrigin-RevId: 167392820
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 167335614
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Change-Id: Ib90ce99cc2e229bbe749130dbde517a075d6e333
PiperOrigin-RevId: 167319258
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke several tests in nightly.
[]
*** Original change description ***
Rollforward #2 of "AppleBinary and AppleStaticLibrary no longer propagate unwrapped ObjcProvider", after changes made to apple bazel rules to be compatible.
RELNOTES: None.
PiperOrigin-RevId: 167312716
|
|
|
|
|
|
|
|
|
|
|
| |
class.
TESTED=Dumped the actions graph for AndroidBinary before and after the change
and compared to make sure the same actions are registered, and also manually
invoked mobile-install.
RELNOTES: None.
PiperOrigin-RevId: 167311030
|
|
|
|
|
|
|
|
| |
We need to ensure that special characters are encoded according to the
URI specification RFC2396.
Change-Id: Ie93cbe11a70f448d2e7bacd0bba5699ec20cac25
PiperOrigin-RevId: 167301074
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167300232
|
|
|
|
|
|
|
|
|
| |
They are unused and the tests depend on Joda Time which I'm going to
remove.
Also document the removal in the package's README.bazel.md.
Change-Id: I7b0ee89718bfc2cffcc60a8262cf53dbf9035669
|
|
|
|
|
|
|
|
|
|
|
| |
testFunctionDictArgumentsAreImmutable
These tests don't actually check mutability of objects but behavior of += on
them. Input arguments of functions are in fact mutable unless they've been
created in another mutability scope. There are already other tests that
actually check immutability of objects from another mutability scope.
PiperOrigin-RevId: 167295711
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel now creates all SpawnActions in
AndroidBinary, AndroidCommon, and DexArchiveAspect
such that they use the default shell environment.
The benefit of this is that these actions will
have a well-controlled, minimal environment, and
most importantly they'll have valid TMP and TEMP
environment variables, which is necessary for temp
file creaion on Windows.
I created this commit for the same reason as
https://github.com/bazelbuild/bazel/commit/0abf5fa2d64c76def5a8fa0f960b73ce0566af4d
See https://github.com/bazelbuild/bazel/issues/3659
Change-Id: Ice42ea6424af8984d3c382ab01727e04cbd0c1b4
PiperOrigin-RevId: 167285724
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Unix-like platforms, we can execute deploy jars
just like normal binaries, but on Windows we
cannot because ".jar" is not an executable
extension. Therefore we cannot run
SingleJar_deploy.jar in a genrule.cmd.
In this change I do the following changes to:
//tools/android/BUILD.tools:
- add a java_import rule that wraps the SingleJar
deploy jar
- add a java_binary that runtime-depends on the
jar
- fix the ":gen_java_lang_extras_jar" genrule to
run the java_binary instead of the deploy jar
See https://github.com/bazelbuild/bazel/issues/3659
Change-Id: Ie035e721deb696bbd4130b3612695a10dd9c2b4d
PiperOrigin-RevId: 167281195
|
|
|
|
|
|
|
|
| |
Let's use the same parser. Dialect differences are checked in a separate
validation pass.
RELNOTES: None.
PiperOrigin-RevId: 167280201
|
|
|
|
|
|
|
|
|
|
|
|
| |
options in emitCompletionHelp().
This change is in preparation for unknown commit which introduces "bazel help flags" -
a new command whose functionality is similar to the existing "bazel help completion".
Both commands have to iterate over Bazel options, which means that applying the visitor patterns helps to avoid duplicate iteration code.
I also tested this change by running "bazel help completion" with and without this change.
PiperOrigin-RevId: 167273874
|
|
|
|
|
|
|
| |
There were a few places where the current state of the world was not clear.
RELNOTES: None.
PiperOrigin-RevId: 167273651
|
|
|
|
|
|
|
|
|
| |
So release are build with -c opt
Fixes #3340.
Change-Id: I455b5c2a53be5fb8fb39e247a849058f19d1d884
PiperOrigin-RevId: 167266776
|
|
|
|
|
| |
Change-Id: I3648aadad5895f80051ada39d0ca862dd437cc58
PiperOrigin-RevId: 167266028
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167263494
|
|
|
|
|
|
|
| |
RELNOTES: None.
Change-Id: Ib5945c36bd2266795005089aab3bf71a857cdf90
PiperOrigin-RevId: 167260570
|
|
|
|
|
| |
Change-Id: I08323cfb98b6d52017bc1285d9d63370a20378eb
PiperOrigin-RevId: 167259969
|
|
|
|
|
|
|
|
|
|
| |
For any errors that are due to failures in the remote caching /
execution layers Bazel now returns exit code 34 (ExitCode.REMOTE_ERROR).
This includes errors where the remote cache / executor is unreachable or
crashes. It does not include errors if the test / build failure is due
to user errors i.e. compilation or test failures.
PiperOrigin-RevId: 167259236
|
|
|
|
| |
Change-Id: I3648aadad5895f80051ada39d0ca862dd437cc58
|
|
|
|
|
|
|
| |
Instead of passing all the runtime jars in the environment variable, we now write them all to a file and store the file path in the env variable, jacoco runner reading the jars from there. Changes on Jacoco runner side are here: https://github.com/bazelbuild/bazel/commit/05418b33dd87d63e2653e594d462b2aedb0e22e5
RELNOTES: A new Java coverage implementation is available. Makes possible coverage for Skylark JVM rules.
PiperOrigin-RevId: 167248966
|
|
|
|
|
|
|
|
|
| |
Adding an event about which completed aspects to expect allows for earlier
feedback of what the aspect is doing. It also allows consumers of the build
event stream to prepare for the TargetCompleted events of the aspect.
Change-Id: I29ef15472867a7169222e0394c7fe061fd1d2994
PiperOrigin-RevId: 167248206
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
fix the downstream breaks that led to the initial rollback
Change-Id: Ib90ce99cc2e229bbe749130dbde517a075d6e333
PiperOrigin-RevId: 167247311
|
|
|
|
|
|
| |
...to not mention a wrong product name.
PiperOrigin-RevId: 167242739
|
|
|
|
|
|
|
|
| |
This will be used to create thin skylark rules to allow for select() on provider values, with xcode_config_alias's XcodeProperties to be the first.
This is demonstrated in XcodeConfigTest.
RELNOTES: None.
PiperOrigin-RevId: 167204266
|
|
|
|
|
|
|
| |
removed in https://github.com/bazelbuild/bazel/commit/ca600bf2d014650b1f1ecb5214878b09a0838086.
RELNOTES: None
PiperOrigin-RevId: 167202392
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks rules_go CI
*** Original change description ***
Rollforward of c++ toolchain-relevant BUILD file and Bazel mocking changes. That is, a c++ toolchain is added, but a Bazel dependency on that toolchain is not.
PiperOrigin-RevId: 167198874
|
|
|
|
|
|
|
|
| |
This feature is opening up beyond just ConfigFeatureFlags, and so should not
be restricted.
RELNOTES: None.
PiperOrigin-RevId: 167195959
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks rules_go CI
*** Original change description ***
Bazel c++ rules depend on a c++ toolchain.
PiperOrigin-RevId: 167191667
|
|
|
|
|
|
| |
incompatible CPU constraints.
PiperOrigin-RevId: 167189106
|
|
|
|
|
|
| |
Check that the option has a non-empty name and that it does not use deprecated categories. While we're at it, check that the names for options that are flags (all but INTERNAL flags, which are not meant to be used on the command line) are sensible.
PiperOrigin-RevId: 167182172
|
| |
|