| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
Add stdout to default XML file and generate XML file on timeout
This time corretly quote XML output:
- Remove invalid UTF-8 characters
- Wrap stdout in a CDATA
Change-Id: I70bf38641d1946418e7b8e3b4e44ba0820e7b3c6
PiperOrigin-RevId: 163317477
|
|
|
|
|
|
|
| |
fix https://github.com/bazelbuild/bazel/issues/3442
RELNOTES:
PiperOrigin-RevId: 163039890
|
|
|
|
|
|
|
| |
Fixes TODO in AndroidRuleClasses.java.
RELNOTES: None
PiperOrigin-RevId: 162955052
|
|
|
|
| |
PiperOrigin-RevId: 162742684
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks XML format when there is weird characters in the output (Jenkins fails to read XML output for re2 test)
*** Original change description ***
Add stdout to default XML file and generate XML file on timeout
This should fix #1027 and get better error result on Jenkins.
Change-Id: I5ce30b64f634e01dd350af10748c4a9455a6bea8
PiperOrigin-RevId: 162598130
|
|
|
|
|
|
|
|
|
| |
BUILD file. They must use "-" instead of "/"
otherwise Bazel believes the linkopts entry
declares a (invalid) label.
Change-Id: I6ad33c3f51c37f59e7d3b92be872fc4e2b27d434
PiperOrigin-RevId: 162597691
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a partial rollback.
I restored the old flags (with PathListConverter),
added the new ones, added deprecation warnings and
annotations, and added code to concat the values
of new and old.
Existing released versions of Bazel should keep
working with the new code until 2018-01-31, i.e.
for the next ~6 months. After that I'll remove the
old flags and the PathListConverter.
*** Reason for rollback ***
Fixed broken integration with release Blaze.
*** Original change description ***
Automated rollback of commit 5752463ece84ebb4fb074888cba57412ab8d86b3.
*** Reason for rollback ***
Broke too many targets.
***
RELNOTES: none
PiperOrigin-RevId: 162587548
|
|
|
|
|
|
|
| |
This should fix #1027 and get better error result on Jenkins.
Change-Id: I5ce30b64f634e01dd350af10748c4a9455a6bea8
PiperOrigin-RevId: 162474168
|
|
|
|
| |
PiperOrigin-RevId: 162194755
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit:
- deprecates PathListConverter
- removes ExistingPathListConverter because it was
not used in production, only tests
- deprecated List<Path> type flags that use
PathListConverter
- introduces new List<Path> type flags next to the
deprecated ones that use @Options.allowMultiple
and convert with PathConverter; the new and old
lists are concatenated, yielding the flag value
PathListConverter and all of its occurrences
should be removed after 2018-01-31 (about 6 months
from now, which is a safe enough timeframe for
everyone to upgrade Bazel so it uses the new-style
flags).
Reason for deprecation is that colon-separated
path lists don't work on Windows because paths
have colons in them.
Since the Android BusyBox is not intended to be
executed by users but by Bazel only, there's no
release notes necessary.
See https://github.com/bazelbuild/bazel/issues/3264
RELNOTES: none
PiperOrigin-RevId: 162193998
|
|
|
|
|
|
|
|
|
| |
Python tests.
RELNOTES: None.
Change-Id: I76c4f11323b1c0690e20d54f129abd671275acb0
PiperOrigin-RevId: 161934858
|
|
|
|
|
|
|
| |
Fixed https://github.com/bazelbuild/bazel/issues/3366
RELNOTES: None
PiperOrigin-RevId: 161926642
|
|
|
|
|
|
|
|
|
|
| |
their own.
The alias_rules.bzl hack is required because Bazel at HEAD needs to be able to be built
with released Bazel, which doesn't know these rules yet.
RELNOTES: None.
PiperOrigin-RevId: 161808672
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently `rlocation` is not defined in the
environment of regular sh_binary rules, only in
tests. So this commit adds an implementation for
it.
See https://github.com/bazelbuild/bazel/issues/3264
Change-Id: I70ecb91cef5e1b66679e6ba04823831183da5cd9
PiperOrigin-RevId: 161775438
|
|
|
|
|
|
|
| |
Should be USE_MSVC_WRAPPER instead NO_MSVC_WRAPPER now.
RELNOTES: None
PiperOrigin-RevId: 161668110
|
|
|
|
|
|
|
|
|
| |
set USE_MSVC_WRAPPER=1 if you still want to use wrapper script.
RELNOTES:
Windows: Wrapper-less CROSSTOOL becomes default now.
set USE_MSVC_WRAPPER=1 if you still want to use wrapper script.
PiperOrigin-RevId: 161654018
|
|
|
|
|
|
|
|
|
|
| |
The existing support for including a flat list of labels was moved to the `srcs` attribute.
See https://github.com/bazelbuild/bazel/issues/3317 for context and motivation.
Closes #3318.
PiperOrigin-RevId: 161645944
|
|
|
|
|
|
|
|
| |
And instead rely on the flags being set in java_toolchain.jvm_opts.
This change is being made in preparation for JDK 9, which replaces
-Xbootclasspath/p with --patch-module.
PiperOrigin-RevId: 161620182
|
|
|
|
|
|
|
|
|
| |
/DNOMINMAX is a very common use and no one has complained about it yet, so keep it in CROSSTOOL
Fixed https://github.com/bazelbuild/bazel/issues/3347
RELNOTES: None.
PiperOrigin-RevId: 161381862
|
|
|
|
|
| |
Change-Id: Ib061c85900e577f3548d47e8fa86086dfec9654a
PiperOrigin-RevId: 161360338
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add extra debugging info to
zip_manifest_creator.sh in case ZIPPER is not
found. This'll help diagnosing
https://github.com/bazelbuild/bazel/issues/3326
RELNOTES: none
Change-Id: I60884b43c1aa10a9f67843628f1fadc74959059d
PiperOrigin-RevId: 161208218
|
|
|
|
|
|
|
| |
After reviewing these options' meanings, I don't think we need to put them in CROSSTOOL. Users can add them in their own BUILD files if needed, so that they don't have to undefine them. See https://github.com/bazelbuild/bazel/pull/3310
RELNOTES: None
PiperOrigin-RevId: 161177879
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now there are 2 ways how to control crosstool patches. If there is
'no_legacy_features' feature defined, no patching will be performed. If there is
not, then depending on whether any c++ action_config is defined one set of
patches is applied, or other set of patches is applied. It's a mess, and in the
most cases, crosstools that do not define 'no_legacy_features' need the full
patching. This cl fixes the crosstools that need the partial patching.
RELNOTES: Crosstool patches are only applied if the toolchain doesn't define
'no_legacy_features' feature.
PiperOrigin-RevId: 160979463
|
|
|
|
|
|
|
|
|
| |
And so does its test.
See https://github.com/bazelbuild/bazel/issues/3264
Change-Id: I32dd906b94747d601254ab55e7962bf6cda058f4
PiperOrigin-RevId: 160953063
|
|
|
|
|
|
|
|
|
| |
BAZEL_PYTHON is no logger needed if we don't use wrapper script.
Also, decode stdout and stderr so that tests work with Python 3.
Change-Id: I61b60775a51f8322b40f7682e6cf3f63e8e8b6cc
PiperOrigin-RevId: 160874163
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Up until now we allowed implicit iteration, e.g.:
flag_group { flag: '%{some_sequence_variable}' }
From now on, snippet above will raise an error. We require explicit
'iterate_over' message, e.g.:
flag_group {
iterate_over: 'some_sequence_variable'
flag: '%{some_sequence_variable}'
}
RELNOTES: Implicit iteration in the CROSSTOOL has been removed, use explicit 'iterate_over' message.
PiperOrigin-RevId: 160871888
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/rules_scala/pull/241
RELNOTES: None
PiperOrigin-RevId: 160692857
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160648364
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cl promotes //tools/osx/crosstool to be fully specified on its own, without
any blaze patches needed. While at it, I (think I) unified objc and c++ coverage
features. Other than coverage, this cl only adds features that bazel would add
otherwise.
Ping #2420
RELNOTES: ObjC and C++ coverage feature is unified under name 'coverage'
PiperOrigin-RevId: 160633192
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce host and target path separation in the
Android incremental_install.py. This will allow
running this script (and use bazel mobile-install)
on platforms with non-POSIX path semantics
(e.g. Windows).
See https://github.com/bazelbuild/bazel/issues/3264
Change-Id: If6ec09f100dd2e0be3389dce25cb1a13305226e9
PiperOrigin-RevId: 160531950
|
|
|
|
|
|
|
| |
This is for debugging https://github.com/bazelbuild/bazel/issues/3273
Change-Id: I84e260ae1a22147fed0cffc2960352c77af2cf58
PiperOrigin-RevId: 160399209
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
test-setup.sh currently uses the test target name as the "name"
attribute in the xml output's "testcase" element. This ensures names
in the xml are unique across the workspace for unsharded
tests. However, sharded tests all end up with the same "name"
attribute. This angers some junitxml processing tools, which can be
quite persnickity about uniqueness. Let's generate unique test names
of the form "mytest_shard_N/M" for sharded tests.
Change-Id: I6ea82f56846b88449da977dc6629a73b695a485e
PiperOrigin-RevId: 160397341
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The android_sdk_repository now uses the native
Android build tools (e.g. aapt.exe, aidl.exe) when
--host_cpu is one of x64_windows{,_msys,_msvc}.
On Linux/MacOS we create a wrapper script for
these tools and data-depend on
SDK/build-tools/VERSION/lib/*, but on Windows we
have no runfiles support and Bazel just creates a
junction to SDK/build-tools, so all the actual
tools are there where the binaries expect them.
Also change the ":fail" target to select srcs on
the host platform and use a .cmd file on Windows.
See https://github.com/bazelbuild/bazel/issues/3264
Change-Id: Ica586fa1fd4914f4795b4387b449f1c5562164e0
PiperOrigin-RevId: 160383278
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a better location and tools/cpp is packaged in embedded_tools that make the test ends-up in embedded_tools, which is requiring network access
to build embedded_tools!
Side-effect: have to correctly mock the bazel workspace file on a couple
of tests.
This is blocking on https://bazel-review.googlesource.com/c/12350/
PiperOrigin-RevId: 160265524
|
|
|
|
|
|
|
|
|
| |
A common extension to junitxml is to provide the duration of each test
case in seconds. Here, we add the duration to the xml file that
test-setup.sh provides if the test driver doesn't generate one.
Change-Id: I25f94f10bb99db7078919f3e0bcdf7bd3cbb637d
PiperOrigin-RevId: 160252993
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/3237
Change-Id: I4befad7a329695a952f792605b4936b93cfa2a7f
PiperOrigin-RevId: 160249037
|
|
|
|
|
|
|
|
|
|
| |
Some projects, eg. TF depends on @bazel_tools//tools/jdk:jni_md_header-<platform>
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/java/src/main/native/BUILD#L70
We already have this for darwin, linux and freebsd, should also provide it for Windows.
RELNOTES: None.
PiperOrigin-RevId: 160248449
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 160156249
|
|
|
|
|
|
|
| |
Deletes last code references to xcodegen tool as well as tool itself.
RELNOTES: None.
PiperOrigin-RevId: 160137807
|
|
|
|
|
|
|
|
|
|
|
| |
Don't add $TMP as cxx_builtin_include_directory, instead use
$TMP/nvcc_inter_files_tmp_dir
as tmp direcotry for nvcc.exe
Fixed https://github.com/bazelbuild/bazel/issues/3202
RELNOTES: None.
PiperOrigin-RevId: 160109290
|
|
|
|
|
|
|
| |
Now the MSVC CROSSTOOL can truly be wrapper-free! \o/
RELNOTES: None.
PiperOrigin-RevId: 159962674
|
|
|
|
|
|
|
|
|
|
|
|
| |
Split original cc_configure.bzl into 4 different files:
lib_cc_configure.bzl: base library for C++ toolchain configuration
unix_cc_configure.bzl: For Unix platforms
osx_cc_configure.bzl: For macOS
windows_cc_configure.bzl: For Windows
Change-Id: I76fa44294c6ca4304f0a94f3a1c57d6e76141667
PiperOrigin-RevId: 159801973
|
|
|
|
|
|
|
|
|
|
| |
This cl finishes the last bit of c++ linking actions migration to crosstool's
action_configs. From now on, the action_config { tool_path: ... } will be used,
instead of top level tool { path: ... }.
RELNOTES: Bazel now uses tools from action_configs in Crosstool by default (as
oposed to using top level tools).
PiperOrigin-RevId: 159677525
|
|
|
|
|
|
| |
Part of #2219.
PiperOrigin-RevId: 159596011
|
|
|
|
|
|
|
|
| |
Tool.AR is used by go rules, and the inconsistency fixed in this cl was causing a bug.
Fixes #3184.
RELNOTES: None.
PiperOrigin-RevId: 159562216
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 159228238
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous registry value we are querying only exists when Visual
Studio is installed. If user only has VC build tools installed and
doesn't set env vars like BAZEL_VS, VS140COMNTOOLS, VC won't be
detected.
HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\VisualStudio\\SxS\\VC7
exists in both situations and works for all VS versions.
Change-Id: I07b5593e882e23fa9e0079e082e6d357b905736d
PiperOrigin-RevId: 158841618
|
|
|
|
|
| |
Change-Id: Ia2510a2b8df728c02f77e2df4effff3232cfe3a2
PiperOrigin-RevId: 158685074
|
|
|
|
|
|
|
| |
Fixes #2904.
RELNOTES: None.
PiperOrigin-RevId: 158516169
|
|
|
|
| |
PiperOrigin-RevId: 158430272
|