| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke internal builds.
--
MOS_MIGRATED_REVID=137959459
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137955061
|
|
|
|
|
|
|
|
|
|
| |
Bypass converting bytes to string - RecordOutputStream is typically used to
wrap stdout/err, which we write bytes to, the string step is waste.
Make defensive copies of byte[]s passed to Event since Event doesn't.
--
MOS_MIGRATED_REVID=137949714
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137944374
|
|
|
|
|
|
|
| |
This CL also contains a small refactoring that should make the introduction of list-int-mulitplication easier.
--
MOS_MIGRATED_REVID=137938998
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137936478
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137935119
|
|
|
|
|
|
|
|
|
|
|
| |
Now this time in the client documentation, since they are not true
anymore as the gRPC mechanism is always the default and there is no
other mechanism to choose.
--
Change-Id: I59d2cf9276764c32b9b28bf5dc2c0ff6777cec40
Reviewed-on: https://bazel-review.googlesource.com/#/c/7031/
MOS_MIGRATED_REVID=137925682
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137886595
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137877037
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Firebase Android libraries contain lots of AARs with manifests that include
${applicationId}. As far as I can tell, tools/android/merge_manifests.py only
allows for substitution of ${packageName} and not arbitrary placeholder
substitution. The new aar_import rule exposes the AARs in <sdk>/extras which
include include the Firebase Android libraries.
RELNOTES: Default android_manifest_merger is now "android" which uses the official Android manifest merger. http://tools.android.com/tech-docs/new-build-system/user-guide/manifest-merger
--
MOS_MIGRATED_REVID=137875695
|
|
|
|
|
|
|
|
| |
No need for the char[] in the middle, prevents us from accidentally modifying
input, or sucking up ram on huge queries.
--
MOS_MIGRATED_REVID=137872573
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137871914
|
|
|
|
|
|
|
|
|
|
| |
This is a workaround for a clang bug. See
https://code.google.com/p/android/issues/detail?id=220159.
RELNOTES: Fix for Android clang++ std::stack segfault on 32bit x86. See https://code.google.com/p/android/issues/detail?id=220159
--
MOS_MIGRATED_REVID=137871199
|
|
|
|
|
|
|
|
| |
These new log statements help in understanding what files trigger the
TimestampGranularityMonitor's wait logic and when the wait is performed.
--
MOS_MIGRATED_REVID=137868235
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Constant metadata" artifacts represent real files whose changes should be
ignored by the build system. However, these artifacts were triggering the
timestamp granularity checks in TimestampGranularityMonitor because the fact
that they were "constant metadata" was not respected. Avoid this so that
their regeneration does not cause the build to unnecessarily stall.
One of these artifacts is the volatile workspace status file, which is
unconditionally updated on each build. Before this fix, "blaze build" would
get stuck for up to a second waiting for file system timestamps to catch up.
With this fix, the artifact is ignored and the wait is gone. This problem
is magnified on macOS where the default HFS+ file system only has
second-level granularity. (This also affects Linux, but because current
Linux file systems have milli/nanosecond-level granularity, the wait imposed
by TimestampGranularityMonitor is minimal and thus not generally noticeable.)
--
MOS_MIGRATED_REVID=137867586
|
|
|
|
|
|
|
| |
predictable iteration order.
--
MOS_MIGRATED_REVID=137864799
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137864618
|
|
|
|
|
|
|
|
|
| |
components.
In other words, ensure that a version number such as "10" is always padded as "10.0" when describing an apple sdk version number.
--
MOS_MIGRATED_REVID=137836480
|
|
|
|
|
|
|
| |
remain unchanged; it is overridden by ios_test "target_device" attribute.
--
MOS_MIGRATED_REVID=137835927
|
|
|
|
|
|
|
| |
rules instead of a soup of methods.
--
MOS_MIGRATED_REVID=137835755
|
|
|
|
|
|
|
|
|
| |
exporting only CcLinkParamsProvider to provide cc-interop (see the current objc_library implementation).
This allows experimental_objc_library to take advantage of ObjcProvider's direct-deps semantics for protos.
--
MOS_MIGRATED_REVID=137826198
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137800285
|
|
|
|
|
|
|
|
|
|
|
|
| |
apple_dynamic_library rules
Provided values propagated from "dylib" dependencies will be compiled against the srcs of the rule, and linked together with the dependencies.
It is worth noting that "dylibs" differs from "deps" in that there is no configuration transition along this edge.
There is more work to be done on this attribute, so it remains undocumented. Namely, symbol deduping between dylib and statically-linked dependencies needs to be addressed.
--
MOS_MIGRATED_REVID=137721599
|
|
|
|
|
|
|
| |
This significantly simplifies several of our modules.
--
MOS_MIGRATED_REVID=137713119
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change introduces a new output of java_binary
on Windows: %{name}.cmd, a Windows-compatible Java
launcher script. This simply calls out to bash.exe
passing the shell launcher we use on other
platforms.
This change allows java_binary to be the
executable of a Skylark action or any SpawnAction.
Fixes https://github.com/bazelbuild/bazel/issues/1925
RELNOTES[NEW]: Bazel on Windows: java_binary can now be a the executable of Skylark rule actions (ctx.action's executable argument)
--
MOS_MIGRATED_REVID=137708331
|
|
|
|
|
|
|
|
|
|
| |
It allows all graph implementations to return the list of nodes which are
immediately available to be fetched. NOTE: Not-currently-available here does
not mean the nodes do not exist in the graph. It simply means they are not
ready to be fetched immediately yet.
--
MOS_MIGRATED_REVID=137701432
|
|
|
|
|
|
|
|
|
| |
If `f` is an object with an attribute `x` which is callable, it's valid now to
call `f.x()` directly (caused a "no function called x" error before because .x
is a attribute, not a method).
--
MOS_MIGRATED_REVID=137698425
|
|
|
|
|
|
|
|
|
|
|
| |
objc_library. That is, a module map is always generated, but modules only
used by the library if module maps are enabled.
This is in contrast with previous behavior, under which modules were always
used.
--
MOS_MIGRATED_REVID=137697659
|
|
|
|
|
|
|
| |
headers pruned by .d pruning to be re-added if they are changed.
--
MOS_MIGRATED_REVID=137697323
|
|
|
|
|
|
|
|
|
| |
Requiring all transitive modules to always be available can lead to long
critical paths and even unnecessary compiles in combination with the
prune_header_modules feature.
--
MOS_MIGRATED_REVID=137696794
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137694143
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137688913
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137682796
|
|
|
|
|
|
|
|
|
|
|
|
| |
The C++ client now talks to the Java server through protobuf messages
using the RPC mechanism provided by grpc, so this AF_UNIX socket file is
not used anymore for the communication between them since commit
a3c4833dc24b: ("Remove support for using AF_UNIX...").
--
Change-Id: Ic71e4c65ebb6bb2e661128635c2440007feaf5f6
Reviewed-on: https://bazel-review.googlesource.com/#/c/7030/
MOS_MIGRATED_REVID=137679905
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137669164
|
|
|
|
|
|
|
| |
RELNOTES: New rule: proto_lang_toolchain(), to support LANG_proto_library rules on multiple platforms.
--
MOS_MIGRATED_REVID=137550563
|
|
|
|
|
|
|
| |
explicitly omitted
--
MOS_MIGRATED_REVID=137547748
|
|
|
|
|
|
|
|
|
| |
download_and_execute().
GITHUB: #1752
--
MOS_MIGRATED_REVID=137535936
|
|
|
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2002
This bug was making
//src/t/j/c/g/d/build/lib/skyframe:SkyframeTests
fail on my Windows machine.
--
MOS_MIGRATED_REVID=137521932
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks blaze_util_test for Bazel https://github.com/bazelbuild/bazel/issues/1999
*** Original change description ***
Uncomment lines inside blaze_util_tests since the tests are now
passing.
--
MOS_MIGRATED_REVID=137516264
|
|
|
|
|
|
|
| |
configure protos intermediate artifacts to use the build configuration, if any provided.
--
MOS_MIGRATED_REVID=137514384
|
|
|
|
|
|
|
| |
to detect whether arg is a valid startup option.
--
MOS_MIGRATED_REVID=137512954
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137506734
|
|
|
|
|
|
|
|
| |
Add the product name to the ConfiguredRuleClassProvider so that the doc
generator can generate the proper links to the user manual.
--
MOS_MIGRATED_REVID=137505460
|
|
|
|
|
|
|
|
|
|
| |
This allow us to keep this logic in one place and add a documentation
for what it means (making it more in sync with its Java counterpart).
--
Change-Id: I20ecfa6ea2cd3129a2f7a920c3bffe532f664a90
Reviewed-on: https://bazel-review.googlesource.com/#/c/6990/
MOS_MIGRATED_REVID=137504319
|
|
|
|
|
|
|
| |
Otherwise, it'd only be reaped by init when the client terminates.
--
MOS_MIGRATED_REVID=137502970
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137495530
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137464177
|