| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out that the SUCCESS status is often misunderstood to mean "zero exit",
even though this is clearly documented. I've decided to add another status for
non-zero exit, and use success only for zero exit to avoid this pitfall.
Also, many of the status codes are set, but never used. I decided to reduce the
number of status codes to only those that are actually relevant, which
simplifies further processing. Instead, we should add a string message for the
error case when we need one - we're not using it right now, so I decided not to
add that yet.
PiperOrigin-RevId: 177129441
|
| |
| |
| |
| |
| |
| |
| | |
so that integration tests can use them.
RELNOTES: None
PiperOrigin-RevId: 177113967
|
| |
| |
| |
| |
| | |
RELNOTES: None.
PiperOrigin-RevId: 177113477
|
| |
| |
| |
| |
| |
| | |
Blaze now passes class paths as individual arguments, instead of a pre-joined.
PiperOrigin-RevId: 177112933
|
| |
| |
| |
| |
| |
| | |
This avoids bazelbuild/bazel#4108.
PiperOrigin-RevId: 177096864
|
| |
| |
| |
| |
| | |
RELNOTES: None
PiperOrigin-RevId: 177068047
|
| |
| |
| |
| |
| |
| |
| |
| | |
It fixes issue #4104 and few on the readme file.
Closes #4131.
PiperOrigin-RevId: 177053228
|
| |
| |
| |
| |
| | |
RELNOTES: None.
PiperOrigin-RevId: 177049661
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this CL with --runs_per_test=10 on 2015 Macbook Pro
INFO: Elapsed time: 622.222s, Critical Path: 314.33s
//src/test/shell/bazel/android:android_ndk_integration_test TIMEOUT in 10 out of 10 in 314.3s
Stats over 10 runs: max = 314.3s, min = 306.1s, avg = 308.9s, dev = 3.5s
After this CL with --runs_per_test=10 on 2015 Macbook Pro
INFO: Elapsed time: 875.356s, Critical Path: 148.11s
//src/test/shell/bazel/android:android_ndk_integration_test PASSED in 148.1s
Stats over 60 runs: max = 148.1s, min = 25.3s, avg = 70.2s, dev = 38.7s
RELNOTES: None
PiperOrigin-RevId: 177048666
|
| |
| |
| |
| |
| | |
RELNOTES: None
PiperOrigin-RevId: 177048616
|
| |
| |
| |
| |
| |
| | |
Closes #4159.
PiperOrigin-RevId: 177033307
|
| |
| |
| |
| | |
PiperOrigin-RevId: 177032673
|
| |
| |
| |
| |
| |
| | |
Closes #4158.
PiperOrigin-RevId: 177028468
|
| |
| |
| |
| |
| |
| | |
Closes #4160.
PiperOrigin-RevId: 177028049
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
using FileValue, rather than FileStateValue, nodes as the roots of the rdep traversal.
This is incorrect e.g. when a .bzl file is a target of a symlink that is load'd from a BUILD file.
RELNOTES: None
PiperOrigin-RevId: 177018264
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
*** Reason for rollback ***
Breaks //javatests/com/google/devtools/intellij/blaze/plugin/aspect/java/soygenrule:SoyGenruleTest
*** Original change description ***
Create the output source jar in java_common.compile
and expose transitive source jars to Skylark.
Slightly refactor java classes to take in specific host javabase inputs and host java executable for creating the source jar, instead of always relying on fetching them from native java rules specific attributes.
Creating the output source jar in java_common.compile makes the behavior more similar to java_library.
Exposing the transitive_source_jars to Skylark helps with the Skylark migration fr...
***
RELNOTES: None.
PiperOrigin-RevId: 177015958
|
| |
| |
| |
| | |
Change-Id: I3deb9b30136f5e5019dca6413251427c0a85ef62
|
| |
| |
| |
| |
| |
| |
| | |
I can't find whether ctx.run() actually exists. https://docs.bazel.build/versions/master/skylark/lib/ctx.html implies it doesn't.
RELNOTES: None.
PiperOrigin-RevId: 177005229
|
| |
| |
| |
| |
| | |
RELNOTES: None.
PiperOrigin-RevId: 177004853
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Baseline: cff0dc94f6a8e16492adf54c88d0b26abe903d4c
Cherry picks:
+ 8a49b156c4edf710e3e1e0acfde5a8d27cc3a086:
Fix ImportError on tools.android for junction_lib
+ 275ae45b1228bdd0f912c4fbd634b29ba4180383:
Automated rollback of commit
4869c4e17d5b1410070a1570f3244148d8f97b5d.
+ d0bf589f2716b3d139c210930371a684c6e158eb:
Add a random number to action temp dir
+ 9738f35abddb7ef7a7ef314b5d2a52a3be1b830a:
CcProtoLibrary: Don't add dynamic librarys to filesToBuild on
Windows
+ 0d6ff477099fdf6c8c1c7d4e2104f9184afe0a2b:
Automated rollback of commit
0ebb3e54fc890946ae6b3d059ecbd50e4b5ec840.
Incompatible changes:
- ctx.fragments.apple.{xcode_version,ios_minimum_os} is not
supported anymore. The same information is accessible through the
target @bazel_tools//tools/osx:current_xcode_config: point an
implicit attribute to it (i.e.
attr.label(default=Label("@bazel_tools//tools/osx:current_xcode_co
nfig")) then use
ctx.attr._xcode_config[apple_common].XcodeVersionConfig].
- ctx.fragments.apple.minimum_os_for_platform_type is not supported
anymore. The same information is accessible through the target
@bazel_tools//tools/osx:current_xcode_config: point an implicit
attribute to it (i.e.
attr.label(default=Label("@bazel_tools//tools/osx:current_xcode_co
nfig")) then use
ctx.attr._xcode_config[apple_common].XcodeVersionConfig].minimum_o
s_for_platform_type .
- ctx.fragments.apple.sdk_version_for_platform is not supported
anymore. The same information is accessible through the target
@bazel_tools//tools/osx:current_xcode_config: point an implicit
attribute to it (i.e.
attr.label(default=Label("@bazel_tools//tools/osx:current_xcode_co
nfig")) then use
ctx.attr._xcode_config[apple_common].XcodeVersionConfig].sdk_versi
on_for_platform .
- --javabase=<absolute path> and --host_javabase=<absolute path>
are not supported anymore. If you need this functionality
java_runtime_suite(name="suite", default=":runtime")
java_runtime(name="runtime", java_home=<path to the JDK>) is an
alternative.
- The flag --incompatible_descriptive_string_representations is no
longer available, old style string representations of objects are
not supported
anymore.
- The flag --incompatible_disallow_set_constructor is no longer
available, the deprecated `set` constructor is not available
anymore.
- += on lists now mutates them. `list1 += list2` is now equivalent
to `list1.extend(list2)` and not equivalent to `list1 = list1 +
list2` anymore.
- the target_apple_env and apple_host_system_env methods on
ctx.fragments.apple are not supported anymore. The same
information is accessible through apple_common.target_apple_env
and apple_common.apple_host_system_env . They need the Xcode
configuration as an argument, which can be obtained by declaring
an implicit dependency on it (i.e.
attr.label(default=Label("@bazel_tools//tools/osx:current_xcode_co
nfig")) and then calling e.g.
apple_common.apple_host_system_env(ctx.attr._xcode_config[apple_co
mmon.XcodeVersionConfig]).
- C++ toolchain identifiers are not in the name of the output
directory anymore.
- Selecting on "xcode_version" and
"{ios,tvos,macos,watchos}_sdk_version" is not supported anymore.
What was config_setting(values={"$FOO_version": $VALUE}) is now
config_setting(flag_values={"@bazel_tools//tools/osx:$FOO_version_
flag": $VALUE}).
- Selecting on "xcode_version" and
"{ios,tvos,macos,watchos}_sdk_version" is not supported anymore.
What was config_setting(values={"$FOO_version": $VALUE}) is now
config_setting(flag_values={"@bazel_tools//tools/osx:$FOO_version_
flag": $VALUE}).
- The flag --incompatible_disallow_set_constructor is no longer
available, the deprecated `set` constructor is not available
anymore.
- Selecting on "xcode_version" and
"{ios,tvos,macos,watchos}_sdk_version" is not supported anymore.
What was config_setting(values={"$FOO_version": $VALUE}) is now
config_setting(flag_values={"@bazel_tools//tools/osx:$FOO_versi...
New features:
- runfiles, sh: Shell scripts may now depend on
//src/tools/runfiles:runfiles_sh_lib and source runfiles.sh. The
script defines the `rlocation` function which returns runfile
paths on every platform.
- 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)
Important changes:
- android_binary now supports custom debug keys via the debug_key
attribute.
- Updated Android proguard to 5.3.3. It now works with android-24+.
- --experimental_use_parallel_android_resource_processing and
--experimental_android_use_nocompress_extensions_on_apk are
removed. These features are fully rolled out.
- Fixes #2574
- Fixes #3834
- Enable experimental UI by default.
- .
RELNOTES: None.
RELNOTES: No.
- Add memory profiler.
- [Bazel] {java,cc}_proto_library now look for dependencies in
@com_google_protobuf, instead of in @com_google_protobuf_$LANG
- Improved merge.sh script in cookbook.
- Fixing regression to --experimental_remote_spawn_cache
- Support for linker scripts in NativeDepsHelper (e.g.,
android_binary)
- Skylark semantics flags now affect WORKSPACE files and repository
rules.
- ctx.outputs.executable is deprecated. Use DefaultInfo(executable
= ...) instead.
- Update "mirror.bazel.build" urls to use https.
- Improve --config logging when --announce_rc is present.
- Document interaction between test_suite and target exclusions
- Replace version numbers for Bazel installers with "<version>"
(because this will change often)
- Published command lines should have improved lists of effective
options.
- --incremental_dexing_binary_types has been removed. All builds
are supported by incremental dexing (modulo proguard and some
blacklisted dx flags).
- Document --host_javabase, --host_java_toolchain
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add CompactSkylarkInfo, which stores its values as an array instead of
a map. The space savings will probably not be dramatic because
providers usually have a limited amount of keys. But, there are a lot
of them!
Change-Id: Idd452a5e3982f773b1c5202c73f3d7031ec022c6
PiperOrigin-RevId: 176995376
|
| |
| |
| |
| |
| |
| |
| | |
Split missing-docstring into missing-module-docstring and missing-function-docstring.
RELNOTES: None.
PiperOrigin-RevId: 176993716
|
| |
| |
| |
| |
| | |
RELNOTES: None.
PiperOrigin-RevId: 176993543
|
| |
| |
| |
| | |
PiperOrigin-RevId: 176987812
|
| |
| |
| |
| |
| | |
RELNOTES: None.
PiperOrigin-RevId: 176899549
|
| |
| |
| |
| |
| | |
RELNOTES: None.
PiperOrigin-RevId: 176877525
|
| |
| |
| |
| |
| |
| | |
RELNOTES:
Add six to deps of has_services=1 py_proto_librarys.
PiperOrigin-RevId: 176873598
|
| |
| |
| |
| |
| | |
RELNOTES:
PiperOrigin-RevId: 176844836
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and expose transitive source jars to Skylark.
Slightly refactor java classes to take in specific host javabase inputs and host java executable for creating the source jar, instead of always relying on fetching them from native java rules specific attributes.
Creating the output source jar in java_common.compile makes the behavior more similar to java_library.
Exposing the transitive_source_jars to Skylark helps with the Skylark migration from the old 'java' provider to JavaInfo.
Progress on #2614.
RELNOTES: transitive_source_jars is now exposed on JavaInfo.
PiperOrigin-RevId: 176844750
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
to rules that use the $(JAVA) or the $(JAVABASE) Make variable.
This is necessary because a future Blaze version will require this for rules that use said Make variables. This incompatible change can be tested today by adding the --noexperimental_enable_jvm_configuration_make_variables command line option to Blaze.
This change is part of a large-scale change ([]
RELNOTES: None.
PiperOrigin-RevId: 176834987
|
| |
| |
| |
| |
| | |
Change-Id: I23754fa72d8f1fbd54fb37df470bc9ccaf0a2849
PiperOrigin-RevId: 176831430
|
| |
| |
| |
| |
| |
| | |
The "$singlejar" attribute was removed in unknown commit.
PiperOrigin-RevId: 176826579
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
This specification is based on Alan Donovan's document: https://github.com/google/skylark/blob/master/doc/spec.md
It removes implementation-specific changes and extensions.
It matches better the Java implementation, and is therefore more useful for
Bazel users. It may also be used by other build systems that intend to be
compatible with Bazel files.
RELNOTES: None.
PiperOrigin-RevId: 176783658
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/0ebb3e54fc890946ae6b3d059ecbd50e4b5ec840.
PiperOrigin-RevId: 176774887
|
|
|
|
|
|
|
| |
Bazel is not reading its value anyway.
RELNOTES: None
PiperOrigin-RevId: 176768851
|
|
|
|
| |
PiperOrigin-RevId: 176759562
|
|
|
|
|
|
|
|
| |
Addresses #4018
Closes #4020.
PiperOrigin-RevId: 176750087
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 176700595
|
|
|
|
|
|
|
|
|
|
|
| |
CppHelper. In CppHelper, CcToolchainProvider and CppConfiguration are used
sepereately, allowing toolchain information to be removed from
CppConfiguration.
This is necessary to introduce hermetic toolchains, which require that
toolchain information be seperated from the configuration, into the c++ rules.
PiperOrigin-RevId: 176694160
|
|
|
|
|
|
| |
deduplicate code.
PiperOrigin-RevId: 176686795
|
|
|
|
|
|
|
|
|
| |
We already handle this properly in the normal case. However, when no attributes
from the new implementation of resource processing are specified, we fall back
to the old version, which didn't handle this.
RELNOTES: none
PiperOrigin-RevId: 176672081
|
|
|
|
|
|
|
|
|
| |
allowMultiple=true
Was filtering for the implicit options in SingleOptionValue, but forgot the check in RepeatableOptionValue. This is now fixed.
RELNOTES: None.
PiperOrigin-RevId: 176669853
|
|
|
|
|
|
|
|
| |
And adjust macOS name
Closes #4019.
PiperOrigin-RevId: 176665076
|
|
|
|
|
|
|
| |
Part of #4128.
Change-Id: I1e043e7290912de5b246dbb8748cb2ad865ce38c
PiperOrigin-RevId: 176664440
|
|
|
|
|
|
|
|
|
| |
and #getDynamicMode to CcToolchainProvider and CppHelper.
Moving toolchain info out of CppConfiguration is required to use platform-based
toolchain resolution in the c++ rules.
PiperOrigin-RevId: 176662686
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Cause rare case of test hanging.
To cherry-pick for #3772
*** Original change description ***
Attempting to fix an occasionally missing stdout from test.xml.
In hello-world_test, when executed inside a docker container, for about 2% of the runs the test.xml has an empty CDATA, instead of the expected "Hello, world!". I'm not sure still what exactly was the bug, but in any case this change simplifies the test execution code line, so if this doesn't fix it, at least further debugging will be easier.
I ran the test in a loop 1360 times, and the error did not reproduce once, which hints to...
***
PiperOrigin-RevId: 176662654
|