This project is mirrored from https://github.com/bazelbuild/bazel.git.
Pull mirroring updated .
- Nov 30, 2018
-
-
Bazel Release System authored
Baseline: 7bf7f031 Cherry picks: + fd523415: update bazel-toolchains pin to latest release Part of changes to allow bazelci to use 0.19.0 configs. RBE toolchain configs at or before 0.17.0 are not compatible with bazel 0.19.0 or above. + 241f28d05424db2d11ee245dc856b992258505e3: Revert "Toggle --incompatible_disable_late_bound_option_defaults flag." + f7e5aef1: Add cc_toolchain targets for the new entries in the default cc_toolchain_suite. + d2920e32: Revert "WindowsFileSystem: open files with delete-sharing" [Breaking changes in 0.20](https://github.com/bazelbuild/bazel/issues?q=is%3Aissue+label%3Abreaking-change-0.20) - [--incompatible_remove_native_http_archive](https://github.com/bazelbuild/bazel/issues/6570). - [--incompatible_remove_native_git_repository](https://github.com/bazelbuild/bazel/issues/6569). - [--incompatible_disable_cc_toolchain_label_from_crosstool_proto](https://github.com/bazelbuild/bazel/issues/6434). - [--incompatible_disable_depset_in_cc_user_flags](https://github.com/bazelbuild/bazel/issues/6384). - [--incompatible_disable_cc_configuration_make_variables](https://github.com/bazelbuild/bazel/issues/6381). - [--incompatible_disallow_conflicting_providers](https://github.com/bazelbuild/bazel/issues/5902). - [--incompatible_range_type](https://github.com/bazelbuild/bazel/issues/5264). [0.20 is a migration window for the following changes](https://github.com/bazelbuild/bazel/issues?q=is%3Aissue+label%3Amigration-0.20) - [--incompatible_use_jdk10_as_host_javabase](https://github.com/bazelbuild/bazel/issues/6661) - [--incompatible_use_remotejdk_as_host_javabase](https://github.com/bazelbuild/bazel/issues/6656) - [--incompatible_disable_sysroot_from_configuration](https://github.com/bazelbuild/bazel/issues/6565) - [--incompatible_provide_cc_toolchain_info_from_cc_toolchain_suite](https://github.com/bazelbuild/bazel/issues/6537) - [--incompatible_disable_depset_in_cc_user_flags](https://github.com/bazelbuild/bazel/issues/6383) - [--incompatible_package_name_is_a_function](https://github.com/bazelbuild/bazel/issues/5827) [Breaking changes in the next release (0.21)](https://github.com/bazelbuild/bazel/issues?q=is%3Aissue+label%3Abreaking-change-0.21) - [--incompatible_use_jdk10_as_host_javabase](https://github.com/bazelbuild/bazel/issues/6661) - [--incompatible_use_remotejdk_as_host_javabase](https://github.com/bazelbuild/bazel/issues/6656) - [--incompatible_disable_sysroot_from_configuration](https://github.com/bazelbuild/bazel/issues/6565) - [--incompatible_provide_cc_toolchain_info_from_cc_toolchain_suite](https://github.com/bazelbuild/bazel/issues/6537) - [--incompatible_disable_depset_in_cc_user_flags](https://github.com/bazelbuild/bazel/issues/6383) - [--incompatible_disallow_data_transition](https://github.com/bazelbuild/bazel/issues/6153) - [--incompatible_package_name_is_a_function](https://github.com/bazelbuild/bazel/issues/5827) - [--incompatible_disallow_slash_operator](https://github.com/bazelbuild/bazel/issues/5823) - [--incompatible_static_name_resolution](https://github.com/bazelbuild/bazel/issues/5637) Incompatible changes: - the --experimental_no_dotd_scanning_with_modules command line argument is not supported anymore. - The --prune_cpp_modules command line option is not supported anymore. - the --experimental_prune_cpp_input_discovery command line option is not supported anymore. New features: - Added support for Android NDK r18. Important changes: - The 'default' parameter of attr.output and attr.output_list is removed. This is controlled by --incompatible_no_output_attr_default - A number of platform-related Starlark APIs which were previously marked "experimental" are now disabled by default, and may be enabled via --experimental_platforms_api - Make legacy-test-support ("legacy_test-<api-level>") from android_sdk_repository neverlink. The legacy test support libraries shouldn't be built into test binaries. To make them available at runtime, developers should declare them via uses-library: https://developer.android.com/training/testing/set-up-project#andr oid-test-base - query remote server Capabilities (per REAPI v2) - CppRules: All cc_toolchains depended on from cc_toolchain_suite.toolchains are now analyzed when not using platforms in order to select the right cc_toolchain. - removed obsolete --explicit_jre_deps flag. - Incompatible flag --incompatible_disable_legacy_cpp_toolchain_skylark_api was flipped. - Improve error messaging when unsupport proguard options are specified at the library level. - Incompatible flag --incompatible_disable_legacy_cpp_toolchain_skylark_api was flipped. - Incompatible flag --incompatible_disable_legacy_cpp_toolchain_skylark_api was flipped. - The --incompatible_disable_late_bound_option_defaults flag has been flipped (#6384) - Incompatible flag --incompatible_disable_legacy_flags_cc_toolchain_api was flipped (#6434) - Fixed issue where ctx.resolve_command created conflicting intermediate files when resolve_command was called multiple times within the same rule invocation with a long command attribute. - Incompatible flag --incompatible_disable_cc_configuration_make_variables was flipped (#6381) - If the --javabase flag is unset, it Bazel locates a JDK using the JAVA_HOME environment variable and searching the PATH. If no JDK is found --javabase will be empty, and builds targeting Java will not be supported. Previously Bazel would fall back to using the embedded JDK as a --javabase, but this is no longer default behaviour. A JDK should be explicitly installed instead to enable Java development - Bazel will now shut down when idle for 5 minutes and the system is low on RAM (linux only). - CROSSTOOL file is now read from the package of cc_toolchain, not from the package of cc_toolchain_suite. This is not expected to break anybody since cc_toolchain_suite and cc_toolchain are commonly in the same package. - All overrides of Starlark's ctx.new_file function are now deprecated. Try the `--incompatible_new_actions_api` flag to ensure your code is forward-compatible. - --incompatible_disable_cc_toolchain_label_from_crosstool_proto was flipped. - Introduce --(no)shutdown_on_low_sys_mem startup flag to toggle idle low-memory shutdown, disabled by default. - --incompatible_disable_cc_toolchain_label_from_crosstool_proto was flipped. - --incompatible_disable_cc_toolchain_label_from_crosstool_proto was flipped. - CppRules: All cc_toolchains depended on from cc_toolchain_suite.toolchains are now analyzed when not using platforms in order to select the right cc_toolchain. - The function `attr.license` is deprecated and will be removed. It can be disabled now with `--incompatible_no_attr_license`. - `range()` function now returns a lazy value (`--incompatible_range_type` is now set by default). - The code coverage report now includes the actual paths to header files instead of the ugly, Bazel generated, virtual includes path. - `--incompatible_disallow_conflicting_providers` has been switched to true - Add new flag `--incompatible_disable_systool_from_configration` to disable loading the systool from CppConfiguration. - Add new flag `--incompatible_disable_sysroot_from_configuration` to disable loading the systool from CppConfiguration. - Sorting remote Platform properties for remote execution. May affect cache keys! - Use different server log files per Bazel server process; java.log is now a symlink to the latest log. This release contains contributions from many people at Google, as well as a7g4 <a7g4@a7g4.net>, Alan <alan.agius@betssongroup.com>, Asaf Flescher <asafflesch@gmail.com>, Benjamin Peterson <bp@benjamin.pe>, Ed Schouten <ed.schouten@prodrive-technologies.com>, George Gensure <ggensure@uber.com>, George Kalpakas <kalpakas.g@gmail.com>, Greg <gregestren@users.noreply.github.com>, Irina Iancu <iirina@users.noreply.github.com>, Keith Smiley <keithbsmiley@gmail.com>, Loo Rong Jie <loorongjie@gmail.com>, Mark Zeren <mzeren@vmware.com>, Petros Eskinder <petroseskinder@users.noreply.github.com>, rachcatch <rachelcatchpoole@hotmail.com>, Robert Brown <robert.brown@gmail.com>, Robert Gay <robert.gay@redfin.com>, Salty Egg <2281521+zhouhao@users.noreply.github.com>.
-
- Nov 28, 2018
-
-
Yun Peng authored
This reverts commit 1a955020. Related: https://github.com/bazelbuild/bazel/issues/6731 Closes #6732. PiperOrigin-RevId: 222958770
-
John Cater authored
Fixes #6662. Closes #6663. PiperOrigin-RevId: 221271701
-
Dmitry Lomov authored
This reverts commit 664e02d4.
-
Googler authored
Part of changes to allow bazelci to use 0.19.0 configs. RBE toolchain configs at or before 0.17.0 are not compatible with bazel 0.19.0 or above. PiperOrigin-RevId: 220085357
-
- Nov 05, 2018
-
-
shahan authored
PiperOrigin-RevId: 220018722
-
- Nov 03, 2018
-
-
cushon authored
PiperOrigin-RevId: 219881070
-
cparsons authored
With this change, FuncallExpression defers to DotExpression in many cases instead of re-inventing dot expresssion evaluation. This removes some of the code duplication between these two classes. Additionally, this avoids creating a BuiltinCallable for selfCall methods of objects. This is a benefit in that it cleans up the code (it removes the need for redundant BuiltinCallable code, to be removed in a future change), and it also prevents creating a superfluous object which is to be immediately discarded. RELNOTES: None. PiperOrigin-RevId: 219877592
-
Googler authored
RELNOTES: None. PiperOrigin-RevId: 219870516
-
ahumesky authored
PiperOrigin-RevId: 219845676
-
cparsons authored
RELNOTES: None. PiperOrigin-RevId: 219835721
-
Loo Rong Jie authored
See #2241 Closes #6251. PiperOrigin-RevId: 219810346
-
- Nov 02, 2018
-
-
Yun Peng authored
Related #4811 clang-cl is a driver program for clang that attempts to be compatible with MSVC?s cl.exe, which means we can just use MSVC's CROSSTOOL with clang-cl.exe. See more from https://clang.llvm.org/docs/MSVCCompatibility.html Closes #6553. Change-Id: I907fc71a51e11c0c204b00c845d14b40e7c9f55f PiperOrigin-RevId: 219798300
-
Robert Brown authored
?d by Java. Closes #6228. PiperOrigin-RevId: 219766676
-
cushon authored
PiperOrigin-RevId: 219740531
-
Liam Miller-Cushon authored
-
corysmith authored
*** Reason for rollback *** Breaking nightlies -- will roll forward when unknown commit goes in. *** Original change description *** Allow the --android_aapt flag to override attribute values. RELNOTES: None PiperOrigin-RevId: 219701427
-
mschaller authored
Also adds a getReverseExpansion method to Artifact.ArtifactExpander, intended for use when creating InputOwners for lost inputs. Clarifies what Skyframe nodes are in the RewindPlan created by ActionRewindStrategy, and why. These are: the node associated with the currently executing (failed) action, the nodes associated with the actions which create the inputs which are lost, and all the nodes between them. The reason: restarting those nodes ensures that reevaluating the current node will also reevaluate the nodes that will recreate the lost inputs. RELNOTES: None. PiperOrigin-RevId: 219696965
-
Googler authored
I had moved up the setting of this.value so that it would be part of the logged error. However, setting this.value prior to this.lastChangedVersion may lead to a race condition, so exceptions are being thrown when they shouldn't be. I will attempt to follow up with a threaded test to catch this. RELNOTES: None. PiperOrigin-RevId: 219694529
-
nharmata authored
sentences to the class javadoc. RELNOTES: None PiperOrigin-RevId: 219685303
-
brandjon authored
*** Reason for rollback *** Breaks the nightly. PiperOrigin-RevId: 219682986
-
jcater authored
This is the rollback of commit 20bfdc67, which in turn rolled back the original commit 19a401c3. This was originally rolled back because breaks external go_rules (https://github.com/bazelbuild/bazel/issues/6283) This is now safe as rules_go has been updated and released. Full downstream test run: https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/551 PiperOrigin-RevId: 219678937
-
dannark authored
RELNOTES: None PiperOrigin-RevId: 219676449
-
brandjon authored
*** Reason for rollback *** Apparent prerequisite to rolling back https://github.com/bazelbuild/bazel/commit/54983e28ad8b46adf90142928e1df82d6dcd2dc4. PiperOrigin-RevId: 219673718
-
felly authored
PiperOrigin-RevId: 219660339
-
Googler authored
PiperOrigin-RevId: 219651406
-
nharmata authored
RELNOTES: None PiperOrigin-RevId: 219651071
-
cushon authored
PiperOrigin-RevId: 219649528
-
nharmata authored
Introduce Either, a simple "sum" type in java. See Chapter 11 in https://www.cs.cmu.edu/~rwh/pfpl/2nded.pdf for a principled treatment of the type theoretic background. RELNOTES: None PiperOrigin-RevId: 219643115
-
- Nov 01, 2018
-
-
rachcatch authored
Closes #6549. PiperOrigin-RevId: 219631485
-
Googler authored
The inline Kotlin language feature causes method implementations to be a part of the jar's compiletime interface. We have a Kotlin compiler plugin that will annotate inlined methods with @KeepForCompile and ijar can use this to include code that is a part of the library's compiletime interface into the stripped jar. This iteration keeps the entire class, in the future it only needs to keep the method implementation and any constant pool entries the method accesses. PiperOrigin-RevId: 219553768
-
cparsons authored
This will lead to simplification of some of the build API code. RELNOTES: None. PiperOrigin-RevId: 219551591
-
corysmith authored
RELNOTES: None PiperOrigin-RevId: 219546241
-
janakr authored
PiperOrigin-RevId: 219545299
-
Googler authored
RELNOTES: None. PiperOrigin-RevId: 219538155
-
juliexxia authored
For skylark rules that are declared build settings, we auto-add a nonconfigurable build_setting_default attribute which must be set on a per target basis. We also add access to the build setting value via the rule context object. All of this functionality is hidden behind the --experimental_build_setting_api flag which by default is flipped off. This includes: - Add a build_setting parameter to starlark rule construction. - If a starlark rule sets the build_setting parameter, auto-add a mandatory 'build_setting_default' attribute of the same type. - Allow the value of a build setting skylark rules to be accessed via ctx.build_setting_value. - Get rid of BuildSettingDescriptor since we don't need both it and BuildSetting. - Add the --experimental_build_setting_api flag to SkylarkSemantics flags. Work towards issue #5577 PiperOrigin-RevId: 219537101
-
janakr authored
Check that we've read all bytes when deserializing. If there are bytes left over, something is wrong. PiperOrigin-RevId: 219532280
-
Googler authored
precious. RELNOTES: None. PiperOrigin-RevId: 219529252
-
Googler authored
RELNOTES: None. PiperOrigin-RevId: 219526770
-
arostovtsev authored
The new log handler changes java.log to a symlink to the latest log file. Old log files will be garbage collected to keep the total size under a limit. As a temporary "escape hatch", in case switching server log handlers causes problems, the old non-rotating log handler can be restored using the --norotating_server_log startup option. This option (and the BazelServerLogModule providing it) will be removed once it's clear that an "escape hatch" is not needed. RELNOTES: Use different server log files per Bazel server process; java.log is now a symlink to the latest log. PiperOrigin-RevId: 219512757
-