| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward of commit 86b4532769c22cca2ed7068a60f3326beaad34af after fixing bad import.
+small misc fixes suggested by critique
*** Original change description ***
Automated rollback of commit 86b4532769c22cca2ed7068a60f3326beaad34af.
*** Reason for rollback ***
Probably breaking //javatests/com/google/devtools/build/lib:Query2Tests
*** Original change description ***
Restructure how universeScope is used when testing configured query to mimick impending changes to the configured query interface (CL/179872445) which will pull build targets out of the query expression.
Fill in testTopLevelTransitions on the way!
PiperOrigin-RevId: 180930388
|
|
|
|
| |
Change-Id: I14256e583d07ebad9a0b525917d25e5cb5f7f684
|
|
|
|
|
|
| |
Fixed a broken link, also applied a couple of minor changes.
PiperOrigin-RevId: 180913699
|
|
|
|
|
|
|
|
|
|
|
|
| |
Refactor the test not to use a for-loop to iterate
over the strategies. This way it's easier to see
from the failure stack trace which strategy it was
exactly that failed.
This is preparation for https://github.com/bazelbuild/bazel/issues/4376
Change-Id: I2004b58957c823701c2d68682e7d8b78e80c834a
PiperOrigin-RevId: 180911370
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
android_instrumentation_test's runfiles, and pass the execpath of aapt_binary to the entry point using the --aapt flag.
This allows android_instrumentation_test to use the dynamically linked AAPT from the user-provided SDK.
The reason for not using %aapt% template expansion in the stub template is because @androidsdk//:aapt_binary is a shell script with hardcoded paths to the actual dependencies in its runfiles directory, but since this binary is called within an android_instrumentation_test's runfiles directory, the nested aapt runfiles directory doesn't exist because runfiles are not nested, but merged.
We can make this work by referring to the actual external/androidsdk/aapt_binary using a `../../` directory traversal, and we can also assume that the aapt_binary is there because android_instrumentation_test merged aapt's runfiles from the SDK.
RELNOTES: None.
PiperOrigin-RevId: 180888739
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Probably breaking //javatests/com/google/devtools/build/lib:Query2Tests
*** Original change description ***
Restructure how universeScope is used when testing configured query to mimick impending changes to the configured query interface (CL/179872445) which will pull build targets out of the query expression.
Fill in testTopLevelTransitions on the way!
PiperOrigin-RevId: 180880350
|
|
|
|
| |
PiperOrigin-RevId: 180878300
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward, add updated Resources.proto.
Branch: pi-release
Repo: platform/frameworks/base
ID: 8552195d338da03df31ec188322ff30e2878d6d2
TAP Presubmit
[]
RELNOTES: New version of aapt2 and Resources.proto.
PiperOrigin-RevId: 180873128
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180857355
|
|
|
|
|
|
|
|
| |
mimick impending changes to the configured query interface (CL/179872445) which will pull build targets out of the query expression.
Fill in testTopLevelTransitions on the way!
PiperOrigin-RevId: 180854150
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180851611
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180849649
|
|
|
|
|
|
|
| |
HostTransition can't be migrated yet because it depends on
BuildConfiguration.
PiperOrigin-RevId: 180842784
|
|
|
|
|
|
|
| |
from the ShellTests catch-all target.
RELNOTES: None.
PiperOrigin-RevId: 180836428
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180826643
|
|
|
|
|
|
|
|
|
| |
more cases.
Part of #4128.
Change-Id: Ife5e4581f91ac07931d193ed5eaa256aab3ad047
PiperOrigin-RevId: 180826445
|
|
|
|
|
|
|
|
| |
This change allows turndown of top-level ObjcProvider propagation by apple_binary via --noexperimental_objc_provider_from_linked.
ios test bundle rules depend on loadable bundle apple_binary, and require the binary's deps' objc providers -- thus this is the only mechanism to propagate these providers.
RELNOTES: None.
PiperOrigin-RevId: 180824037
|
|
|
|
|
|
| |
RELNOTES: Remove defunct flags --experimental_incremental_dexing_for_lite_proto and --experimental_incremental_dexing_error_on_missed_jars that have long been enabled by default
PiperOrigin-RevId: 180821902
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Newly discovered bugs indicate that density filtering in analysis does not
cover all cases. Filter in execution as a workaround for these cases. This will
let us turn resource filtering in analysis on and avoid these bugs. (I will
work on actually fixing these bugs in parallel.)
Non-density filtering already runs in execution, even when already filtering in
analysis, due to known limitations of filtering in analysis. (Specifically,
aapt filters more strictly than android_ide_common, and also needs the resource
filters passed anyway to generate pseudolocalized resources.)
RELNOTES: none
PiperOrigin-RevId: 180806206
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create a PosixLocalEnvProvider and
WindowsLocalEnvProvider class, with singleton
instances for now.
This refactoring should not change functionality,
it's just a requirement for an upcoming change.
That upcoming change is for these classes to
respect the client environment's TMPDIR or
TMP/TEMP envvars.
See https://github.com/bazelbuild/bazel/issues/4376
Change-Id: I032bb6f18adf8af9e43e6bc543c09c58adae3863
PiperOrigin-RevId: 180799936
|
|
|
|
|
|
|
| |
* Adds an interface, InjectingObjectCodec, taking an injected parameter in its deserialize method.
* Adds the annotation, @AutoCodec.Dependency, that can be used to indicate that a constructor parameter is a dependency instead of a normal parameter.
PiperOrigin-RevId: 180797816
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Merge the test methods into one test method, in
order to reuse the workspace and the Bazel server.
Add an input file to the mock build rules and
update it before each build, to ensure that Bazel
reruns the actions and uses the strategy-specific
temp directory.
This change reduces the test's runtime on Linux
from 20.2s to 14.7s (average of 5 runs each).
Change-Id: Ia2a8d477d13271af59cdf55cdc49f137460a1b96
PiperOrigin-RevId: 180796797
|
|
|
|
|
|
|
|
|
|
| |
This fixes:
[f for dep in ctx.attr.srcs for f in dep.proto.transitive_imports]
type 'depset' is not iterable. Use the `to_list()` method to get
a list.
Change-Id: I72b8c1c788a5c193af4d4293f0cf81ba4f0da1c6
|
|
|
|
| |
Change-Id: I232828d44447ee66019ff0fedb5ebc18b2e7aee9
|
|
|
|
|
|
| |
Follow-up to 55828e256af4fe04e95f1c342a73d649d8525435.
Change-Id: Ie765f0797e8b85c3c8cb7735f11e021912de3de5
|
|
|
|
| |
Change-Id: Iabf2d196d5050ab5ac81534663f655d80ba21e41
|
|
|
|
|
|
|
| |
This fixes "type 'depset' is not iterable. Use the `to_list()` method
to get a list." warning.
Change-Id: I10bd791ce15445469afb9e12b2246be583c77a4b
|
|
|
|
|
|
|
| |
Fixup from copy-paste in c5672f8edb1cb9fb7806024706d776901d7d434e ("Add the option for warning-level enforcement of One Version violations.")
Change-Id: I90909b2f14aa7a8e0beadb99a72c25ab71bc40d8
PiperOrigin-RevId: 180779047
|
|
|
|
|
| |
Change-Id: Icd1b527798df46d54cb5fd43e37f6211834ad0a6
PiperOrigin-RevId: 180761791
|
|
|
|
|
|
|
|
| |
Makes GlobDescriptor directly implement SkyKey and adds custom serialization
logic. This lets us narrow visibility and migrate yet another SkyKey away from
LegacySkyKey.
PiperOrigin-RevId: 180705483
|
|
|
|
|
|
|
|
|
| |
The `+` operator on dicts is deprecated and will be removed. This change makes
Bazel files compatible with the new behavior.
Fixes #4346.
PiperOrigin-RevId: 180702882
|
|
|
|
| |
PiperOrigin-RevId: 180697983
|
|
|
|
|
|
| |
Uses the constructor having the @AutoCodec.Constructor annotation to generate a codec (instead of choosing the first in source code). This annotation is required when a class has more than one constructor.
PiperOrigin-RevId: 180685902
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We used to have --cpu=x64_windows_msys for selecting msys gcc toolchain,
this is a misuse of --cpu flag.
Instead, we should use --compiler flag to select C++ toolchain.
For example, --compiler=msvc-cl, --compiler=msys-gcc, --compiler=mingw-gcc
After this change, we can use mingw gcc toolchain by following steps:
1. In MSYS, install mingw by `pacman -S mingw-w64-x86_64-gcc`
2. Add /mingw64:/mingw64/bin into PATH
3. build with --compiler=mingw-gcc
Related:
https://github.com/bazelbuild/rules_go/issues/736
Change-Id: I4b5f77ce0698cfcafefe5d2ab17657f9c9e295d3
PiperOrigin-RevId: 180678829
|
|
|
|
|
|
|
|
|
| |
Also remove experimental tag from platform and toolchain flags in docs.
Fixes #4372.
Change-Id: I4e8f29273b52fbaabf9c97d1a7563f817601653f
PiperOrigin-RevId: 180678722
|
|
|
|
|
|
| |
conveniently also makes it unnecessary to pass the entire LoadingResult when doing configured queries post analysis.
PiperOrigin-RevId: 180676481
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When --nobuild_runfile_manifests is passed, don't create runfiles
input or output manifests at all. This seems better than creating fake
manifest artifacts that are actually a middleman. Fail fast for local
tests and the run command when --nobuild_runfiles_manifests is
passed. (These cases were failing with obscure errors before under
--nobuild_runfile_manifests-I just improved the messaging. See
https://github.com/bazelbuild/bazel/issues/4177.)
Change-Id: I351d26f746ecbe47016b58e4662768a5b6a72ff2
PiperOrigin-RevId: 180659571
|
|
|
|
|
|
| |
Closes #4352.
PiperOrigin-RevId: 180659440
|
|
|
|
|
|
|
|
| |
This is fast (profiles indicate a 9% penalty vs getters) and does not require getters.
* Also adds a Marshaller for java.util.regex.Pattern.
* Minor fixes for codecs that were broken by this change.
PiperOrigin-RevId: 180619680
|
|
|
|
|
|
|
| |
that most Google builds have it set to true.
RELNOTES: None
PiperOrigin-RevId: 180578926
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 180562543
|
|
|
|
|
|
|
| |
The said test fails if the --incompatible_disallow_dict_plus flag is flipped by
default (e.g. in a .bazelrc file)
PiperOrigin-RevId: 180553910
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel's autoconf script adds -fno-canonical-system-headers to gcc's crosstool
in order to get output in '.d' files that can be properly verified by bazel.
To workaround the same issue in clang we have to use a different flag:
'-no-canonical-prefixes'.
The same issue arises with clang if it resides in the configured repository
(e.g., when it is downloaded via 'repository_ctx.download').
PiperOrigin-RevId: 180552155
|
|
|
|
|
|
|
|
|
| |
This change avoids the need to inject the user's
JAVA_HOME into the test, or to discover the JDK's
location on Windows.
Change-Id: Icec2f23ff61d52406eabe36367130d00535d8764
PiperOrigin-RevId: 180547577
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Generated crosstool previously used absolute paths for everything.
However, when using a compiler, local to the repository (e.g., downloaded via
'repository_ctx.download'), relative paths should be used to avoid absolute
paths that point into the crosstool repository.
Specifically, this patch contains the following changes:
1. Replaces absolute paths in 'cxx_builtin_include' with relative if includes
point inside the repository.
2. Removes the '-B<compiler-dir>' from 'compiler_flag' and 'linker_flag'
sections when compiler is inside the repository.
PiperOrigin-RevId: 180540359
|
|
|
|
|
|
|
|
| |
This fixes //src/test/docker/test_cc_configure-fedora23-fastbuild after
https://github.com/bazelbuild/bazel/commit/2aeaeba66857c561dd6d63c79a213f1cabc3650d.
RELNOTES: None.
PiperOrigin-RevId: 180535604
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
causes github #4375 and #4373
*** Original change description ***
Use an annotation preprocessor to validate SkylarkConfigurationField.
RELNOTES: None.
PiperOrigin-RevId: 180535458
|
|
|
|
|
|
|
|
|
|
| |
When a source jar is used as maven_jar the filegroup in the generated BUILD.bazel contains duplicate entries. This results in an error when the jar is used as a dependency (... is duplicated in the 'srcs' attribute of rule 'file').
This change simply doesn't write the duplicate entry to the BUILD.bazel file when the filenames are equal.
Closes #4333.
PiperOrigin-RevId: 180534960
|
|
|
|
|
|
|
|
|
|
|
|
| |
When --define EXECUTOR=remote is specified in bazel command, embedded
tools 'def_parser' will be compiled remotely from source.
Because def_parser itself is a cc_binary, if we want to compile it
remotely, to avoid cycle dependency it cannot be a dependency of
cc_toolchain. Therefore, we make it a dependency of cc rules.
Change-Id: I77faf77238f8edd3585d0e5e5c780b14e9782a40
PiperOrigin-RevId: 180534568
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This rule enables testing android_librarys locally in the jvm (as opposed to on a device). To use this rule with robolectric (robolectric.org), add the following to your WORKSPACE file:
http_archive(
name = "bazel_android",
url = "...",
)
load("@bazel_android//:setup_robolectric.bzl", "setup_robolectric")
setup_robolectric()
and then an android_local_test rule would need to add:
"@bazel_android//:robolectric",
to its dependencies.
android_local_test(
name = "MyTest",
srcs = ["MyTest.java"],
deps = [
"//java/app:lib",
"@bazel_android//:robolectric",
],
)
RELNOTES[NEW]: New android test rule, android_local_test.
PiperOrigin-RevId: 180438995
|