| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
This includes tests for the feature in https://github.com/bazelbuild/bazel/issues/1936.
RELNOTES: None
PiperOrigin-RevId: 152734391
|
|
|
|
|
|
|
|
|
|
| |
Previously, there was no configuration transition in the default case.
While this was "convenient" for testing, it makes these tests somewhat inconsistent,
and furthermore invalid once these rules switch to always using a configuration transition
with the inclusion of minimum OS as an attribute.
RELNOTES: None.
PiperOrigin-RevId: 152734307
|
|
|
|
| |
PiperOrigin-RevId: 152729637
|
|
|
|
| |
PiperOrigin-RevId: 152714468
|
|
|
|
|
|
|
| |
--j2objc_dead_cdoe_report accepts a label that can generate a dead code report as argument. If specified, Blaze should pass "--dead-code-report path/to/dead/code/report" to J2ObjC.
RELNOTES: None.
PiperOrigin-RevId: 152712841
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously multidex did not work in Bazel because it required a dependency on
zip, which we do not ship with Bazel. Then the
--experimental_android_use_singlejar_for_multidex flag was added to use a
different tool that is included with Bazel for multidex. This change sets that
flag to be the default.
Fixes https://github.com/bazelbuild/bazel/issues/1936
RELNOTES: android_binary multidex should now work without additional flags.
PiperOrigin-RevId: 152712301
|
|
|
|
|
|
|
| |
This is not exhaustive of all combinable attributes, but of those that have common uses. More combinable attributes can be added by adding to ResourcesAttribute.AttributeType.
RELNOTES: None.
PiperOrigin-RevId: 152694650
|
|
|
|
|
| |
Change-Id: I407240708f4aacc89ec5c00bf3e8ff46a1d6d6d6
PiperOrigin-RevId: 152692981
|
|
|
|
|
|
| |
By the time the invocation policy gets enforced, the expansion flag should have been
expanded, and policy should act as on any other expansion flag.
PiperOrigin-RevId: 152692831
|
|
|
|
|
|
|
|
| |
In this way, shared subsets of artifacts are only reported once,
even if occurring for many aspect-target pairs.
Change-Id: Ia300126f427af4a9cc630fbfca649760d8b72262
PiperOrigin-RevId: 152692099
|
|
|
|
|
|
|
| |
Only checking for GitHub right now, this could probably be expanded.
Fixes #2147
PiperOrigin-RevId: 152689610
|
|
|
|
|
|
|
|
| |
To avoid artifacts rolled up from other targets to be reported several
times.
Change-Id: I8a329f1c53ad3fcb37cc6602b906472dfce1a12f
PiperOrigin-RevId: 152688681
|
|
|
|
|
|
|
| |
GroupedListHelper
RELNOTES: None
PiperOrigin-RevId: 152687516
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 152686923
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Newer versions of docker require 'sha256' prefix with full IDs (see
https://github.com/docker/docker/issues/20972#issuecomment-193381422). Without
the prefix users get the following error with newer versions of docke, e.g. 17.04.0-ce-rc1:
$ docker tag 7cd4bfeb6766d1c5e5d729b7444cba3d9f97dfddfbeab90ed2e3f7147804ee8f \
docker.io/<user>/<image>:<tag>
Error parsing reference:
"7cd4bfeb6766d1c5e5d729b7444cba3d9f97dfddfbeab90ed2e3f7147804ee8f"
is not a valid repository/tag: invalid repository name
(7cd4bfeb6766d1c5e5d729b7444cba3d9f97dfddfbeab90ed2e3f7147804ee8f),
cannot specify 64-byte hexadecimal strings
---
I'm not sure if this is the proper solution, but it seems to fix the problem with docker version `17.04.0-ce-rc1` as well as older docker version (e.g. `1.12.0`). Alternative solutions welcome.
Closes #2755.
PiperOrigin-RevId: 152685896
|
|
|
|
|
|
|
| |
More info here #2583
Closes #2679.
PiperOrigin-RevId: 152685327
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add stricter error checks in hopes of catching
occasional CI flakiness where the stdout of a
command seems to get lost.
It's now an error if the command returns a
non-zero exit code (or a zero one if it's expected
to fail) or if its stdout is empty. Previously we
only checked if stderr was empty to consider the
action successful.
See https://github.com/bazelbuild/bazel/issues/2675
RELNOTES: none
PiperOrigin-RevId: 152685220
|
|
|
|
| |
PiperOrigin-RevId: 152684266
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1586
RELNOTES: none
PiperOrigin-RevId: 152679734
|
|
|
|
|
|
|
| |
fprintf(stderr, "\nCannot write to %s; exiting...\n\n", broken_pipe_name);
Closes #2736.
PiperOrigin-RevId: 152675241
|
|
|
|
|
|
|
| |
It doesn't make sense, and is ignored anyway.
RELNOTES: None.
PiperOrigin-RevId: 152667088
|
|
|
|
| |
PiperOrigin-RevId: 152663008
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This addresses #2761, to provide a minor improvement if neither `gcc` or `CC` are found on the path.
Let me know if you would like anything changed!
Local qualification steps:
```
$ cd bazel
$ git rebase 0.4.5 # Did not want to spend too much time synchronizing derived stuff in master
$ ln -s ~/Downloads/bazel-0.4.5-dist/derived .
$ ./compile.sh
$ export PATH=~+/output/bazel;$PATH
$ cd .../someproject
$ CC=clang-9000 bazel build //package:test
Cannot find gcc or CC (clang-9000), either correct your path or set the CC environment variable.
```
Closes #2773.
PiperOrigin-RevId: 152658002
|
|
|
|
| |
PiperOrigin-RevId: 152654844
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 152561328
|
|
|
|
|
|
|
|
|
|
|
| |
The only difference in the crosstool is the clang version. See the full NDK14 changelog here:
https://github.com/android-ndk/ndk/wiki/Changelog-r14
Fixes https://github.com/bazelbuild/bazel/issues/2655.
RELNOTES: Bazel now supports Android NDK14.
PiperOrigin-RevId: 152552865
|
|
|
|
|
|
| |
when change pruning. This can speed up change pruning.
PiperOrigin-RevId: 152538144
|
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 152525831
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 152523635
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Causes Blaze release failures.
*** Original change description ***
Genrules only depend on the host JDK if they have Java make variables.
e.g.: cmd = "$(JAVA) foo.java ..."
PiperOrigin-RevId: 152516143
|
|
|
|
|
|
|
| |
necessary with dynamic configurations
RELNOTES: None.
PiperOrigin-RevId: 152515642
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This gives the ability to select on config_feature_flags. They still
have not been publicly documented, because there's no way to set them.
But, progress.
config_setting still needs to have either values or flag_values; it cannot
have both be empty. However, values is no longer mandatory, nor must it be
nonempty (as long as flag_values is set nonempty).
RELNOTES: None.
PiperOrigin-RevId: 152515036
|
|
|
|
|
|
|
| |
Previously it returned a frozen list. Using frozen mutables as part of the API specification is an unnecessary complication and should be avoided.
RELNOTES[INC]: The return type of depset.to_list() is now a list rather than a frozen list. (Modifying the list has no effect on the depset.)
PiperOrigin-RevId: 152504943
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, increase the rate limit for updates to the progress
bar over time, if it cannot be updated in place. In this way, we can get snappy
first progress descriptions, while not overwhelming the user with too many progress
messages.
Change-Id: I769f1a9ef4304b613d40ece42b87df22881549cd
PiperOrigin-RevId: 152502295
|
|
|
|
|
|
|
| |
All android_sdk rules are required to have the apksigner binary, which was not included in the build tools until version 24.0.3. So this check is no longer necessary. Instead, we check in AndroidSdkRepositoryFunction.
RELNOTES: None
PiperOrigin-RevId: 152498753
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change, suggested by @tylerfox at
https://github.com/tensorflow/tensorflow/issues/851#issuecomment-230810921
allows Bazel 0.4.5 to be built on a Jetson TX1 with JetPack 3.0.
The other of @tylerfox's suggested changes was made in 7c4afb6.
Refs #1264
Closes #2703.
PiperOrigin-RevId: 152498304
|
|
|
|
|
|
|
|
|
|
| |
Extend the functionality of the BuildEventStreamer to report those parts
of NestedSets of Artifacts not reported earlier. In this way, duplicate
reporting can be avoided, without the events themselves having to know
which artifacts are known already.
Change-Id: Ia959c28c440301860eac57ea5d9a712c0d49ebdf
PiperOrigin-RevId: 152497672
|
|
|
|
| |
PiperOrigin-RevId: 152497640
|
|
|
|
|
| |
This is ported from StandaloneSpawnStrategy.
PiperOrigin-RevId: 152493898
|
|
|
|
|
|
|
|
|
| |
macOS version strings that have only two components, e.g. "10.12", were
always failing the check that the macOS version is >= 10.11, causing
Bazel to erroneously think sandboxing isn't supported
Change-Id: Ifa4a01fc304e7620502d3f0f9f70c3b500d23864
PiperOrigin-RevId: 152493682
|
|
|
|
| |
PiperOrigin-RevId: 152491822
|
|
|
|
|
|
|
|
| |
Usually, Bazel creates the sandbox directories underneath its
output_base. With --experimental_sandbox_base you can specify a
different parent directory for this, e.g. /dev/shm to run all sandboxed
actions on a memory-backed filesystem.
PiperOrigin-RevId: 152490815
|
|
|
|
|
|
|
| |
They need to explicitly request a minimum iOS version of 8.0 to work with Xcode 8.3, otherwise they fail with this error:
ld: embedded dylibs/frameworks are only supported on iOS 8.0 and later (@rpath/XCTest.framework/XCTest) for architecture x86_64
PiperOrigin-RevId: 152489692
|
|
|
|
|
|
|
| |
Write a new function that dedupes a set of paths using its canonical
form and use it to remove possible duplicates in the set of rc files
that will be parsed.
PiperOrigin-RevId: 152489149
|
|
|
|
|
| |
Closes #2645.
PiperOrigin-RevId: 152488176
|
|
|
|
|
| |
Closes #2728.
PiperOrigin-RevId: 152487667
|
|
|
|
|
|
|
|
|
| |
The LocalSpawnRunner is a non-sandboxed local execution implementation, which
will replace the current StandaloneSpawnStrategy. The code has been around for
a long time and has seen a lot of bugfixes. It also supports local prefetching,
which is required for Google. I have a follow-up change to make it support
Windows, so it's not a drop-in replacement for StandaloneSpawnStrategy yet.
PiperOrigin-RevId: 152486973
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes https://github.com/bazelbuild/bazel/issues/2660. Basically,
if we elect to keep the journal during PersistentMap.save(), we
shouldn't stomp over it the next time save() is called.
In writeJournal(), we now check if the journal file exists, and open
it in append mode if it does. Alternatively, we could simply not close
(and thus forget about) the journal in save(), but that would leak the
journal file handle if save() was never called with keepJournal()
returning false.
Change-Id: Id00732f161c8b5a082a6c109aee115591ace2ea7
PiperOrigin-RevId: 152480978
|
|
|
|
| |
PiperOrigin-RevId: 152468763
|