| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was a crash when the starting point of a negative slice is larger than
the list length.
In addition, there was an incorrect result when the ending point of a negative
slice is less than the list's length times -1. It would wrongly exclude the
first element.
RELNOTES: Fix slicing bug where "abc"[:-4:-1] would give wrong answer
--
MOS_MIGRATED_REVID=138878716
|
|
|
|
|
|
|
|
|
|
| |
...as opposed to //src/test/cpp:blaze_util_test which works
fine.
--
Change-Id: I1e629e6f8eda47cd7eac11511d54ee23f7122848
Reviewed-on: https://bazel-review.googlesource.com/#/c/7335
MOS_MIGRATED_REVID=138871238
|
|
|
|
|
|
|
|
|
| |
correct behavior in dotd pruning after a bazel shutdown - the action will
realize that its inputs are not known and will consult the on-disk action
cache.
--
MOS_MIGRATED_REVID=138868221
|
|
|
|
|
|
|
| |
headers pruned by .d pruning to be re-added if they are changed.
--
MOS_MIGRATED_REVID=138866385
|
|
|
|
|
|
|
|
|
| |
...as it fails to compile.
--
Change-Id: I9040f953235fd71b1d5cfc2bb3dbcba9182ad085
Reviewed-on: https://bazel-review.googlesource.com/#/c/7334
MOS_MIGRATED_REVID=138865280
|
|
|
|
|
|
|
| |
Fixes #2041.
--
MOS_MIGRATED_REVID=138865231
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138863855
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138860974
|
|
|
|
|
|
|
| |
If the --build_tag_filters option is specified, targets built will be filtered according to their tags (at least one included, none excluded)
--
MOS_MIGRATED_REVID=138856195
|
|
|
|
|
|
|
|
|
|
| |
Introduced by commit 9c95196bf21e42bf46df9436a84d263c26e972d2.
Tested:
"bazel build --nobuild //src/{main,test}/cpp/...:all"
--
MOS_MIGRATED_REVID=138855659
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
junitrunner/java/com/google/testing/junit/runner/sharding/weighted has an internal reference that is not easy to open-source. For now it makes more sense to roll this back and keep this package just internally.
*** Original change description ***
Open sourcing junitrunner/java/com/google/testing/junit/runner/sharding/weighted.
--
MOS_MIGRATED_REVID=138852305
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cl adds a 3rd type of build variable - structs. Structs have fields, which
can hold any build variable type (including structs). In the CROSSTOOl, the
fields are accessed by the dot-notation, e.g.:
flag_group {
iterate_over: "libraries_to_link
flag_group {
iterate_over: "libraries_to_link.libraries"
flag: "-L%{libraries_to_link.libraries.directory}"
}
}
As a memory optimization, we also add StructureSequences. These save us from
the overhead of individual StructureValue objects.
--
MOS_MIGRATED_REVID=138851774
|
|
|
|
|
|
|
|
|
| |
to action_listener() rules.
RELNOTES: Extra actions now contain aspect-related information.
--
MOS_MIGRATED_REVID=138832922
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138831285
|
|
|
|
|
|
|
|
|
|
|
| |
BUILD.
Fixes #552.
RELNOTES[NEW]: Packages are defined in BUILD.bazel as well as BUILD files.
--
MOS_MIGRATED_REVID=138828981
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138816624
|
|
|
|
|
|
|
|
|
|
| |
The intention is to use filegroup's instead.
The motivation is to avoid materializing the transitive srcs of a proto_library, which might be large. Using a filegroup makes it explicit that we only take the listed files into account.
RELNOTES: Blacklists for proto_lang_toolchain() no longer have to be proto_library's.
--
MOS_MIGRATED_REVID=138784908
|
|
|
|
|
|
|
|
|
|
| |
It was copying $XML to $XML.bak, then piping the output of that (the empty
string) through the seds.
Relevant to #2070.
--
MOS_MIGRATED_REVID=138783941
|
|
|
|
|
|
|
| |
expensive parallel operations can operate on at once.
--
MOS_MIGRATED_REVID=138779172
|
|
|
|
|
|
|
| |
Fixes #2067.
--
MOS_MIGRATED_REVID=138762258
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138757881
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change:
- starts using blaze_util::CanAccess and
blaze_util::PathExists instead of access(2)
- implements and starts using blaze_util::GetCwd
instead of getcwd(2)
- implements and starts using
blaze_util::ChangeDirectory instead of chdir(2)
- adds tests for the new wrapper methods
--
MOS_MIGRATED_REVID=138750297
|
|
|
|
|
|
|
| |
--
Change-Id: Iac9d4202e83853d9c796e517847131de3ca7c5e2
Reviewed-on: https://bazel-review.googlesource.com/#/c/7331
MOS_MIGRATED_REVID=138743393
|
|
|
|
|
|
|
| |
not quoted or escaped.
--
MOS_MIGRATED_REVID=138717385
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138700111
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138695951
|
|
|
|
|
|
|
| |
at most K unique things at once.
--
MOS_MIGRATED_REVID=138684040
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138680612
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138669967
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/java/com/google/devtools/build/lib:analysis_test
...to avoid occasional timeout failures on CI.
--
Change-Id: I176b5265284ffd89bcbe85c74b2a5bdc43857c6d
Reviewed-on: https://bazel-review.googlesource.com/#/c/7224
MOS_MIGRATED_REVID=138628567
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138625702
|
|
|
|
|
|
|
|
|
| |
doesn't conflict with whatever AutoValue version the code under test has.
Fixes #2044.
--
MOS_MIGRATED_REVID=138618191
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit repurposes file_posix.cc to be the
POSIX API file handling implementation, and adds
file_windows.cc for the Win32 API implementations.
Furthermore it introduces file_platform.h that
declares the interface.
Subsequent changes will replace POSIX API calls in
the rest of the C++ code with these abstract
methods.
Motivation: our code is so littered with
POSIX-isms that we need an abstraction layer if we
hope to compile it with MSVC.
--
MOS_MIGRATED_REVID=138615822
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this commit:
- update GetOutputRoot with a MSVC-specific code
path, plus add more env vars to check for the
temp directory path in the MSYS-specific code
path
- add error handling to GetSelfPath
--
MOS_MIGRATED_REVID=138611621
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/561.
To use this rule, you will need to include the following line in your WORKSPACE file:
load("@bazel_tools//tools/build_defs/repo:maven_rules.bzl", "maven_aar")
After that, you can use the maven_aar repository rule in your WORKSPACE file as such:
maven_aar(
name = "facebook_android_sdk",
artifact = "com.facebook.android:facebook-android-sdk:3.19.0",
)
Then in your BUILD files, your android_library and android_binary targets can depend on the AAR with the following syntax:
android_binary(
name = "my_app",
...
deps = [
"@facebook_android_sdk//aar",
...
],
)
The resources, classes and native libs from the AAR will be provided. Note however that some features of AAR files are not yet supported, including assets, Proguard maps and lint jars.
--
MOS_MIGRATED_REVID=138575421
|
|
|
|
|
|
|
|
|
|
|
| |
extra-actions for actions registered by Aspects injected by a top-level rule.
Because we can't know whether an aspect was injected by a top-level target or one of its children, we approximate it by only reporting extra-actions from Aspects that the top-level target could have injected.
RELNOTES: When --experimental_extra_action_top_level_only, Bazel reports extra-actions for actions registered by Aspects injected by a top-level rule (approximately).
--
MOS_MIGRATED_REVID=138570606
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138556910
|
|
|
|
|
|
|
| |
the scope and the parser prefix, both of which are final, it never changes.
--
MOS_MIGRATED_REVID=138536185
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138534021
|
|
|
|
|
|
|
|
| |
-Xlintdoc:reference causes javac to load symbols referenced in javadoc, which
may fail with the reduced classpath optimization enabled.
--
MOS_MIGRATED_REVID=138529301
|
|
|
|
|
|
|
| |
owners of actions.
--
MOS_MIGRATED_REVID=138522535
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks several tests under //devtools/ide/eclipse/aspects as shown by the nightly []:
[]
*** Original change description ***
Restrict google_glob_information to eclipse_aspect.
'--legacy_expose_globs' flag has no effect now.
--
MOS_MIGRATED_REVID=138517258
|
|
|
|
|
|
|
| |
--
Change-Id: I908020889a0c573af401d67e988c41d33c654015
Reviewed-on: https://bazel-review.googlesource.com/#/c/7223
MOS_MIGRATED_REVID=138508319
|
|
|
|
|
|
|
|
|
| |
...to avoid occasional timeouts on ci.
--
Change-Id: Ic3fcd90a0a3dc7cbdf5d3669733417d181df6491
Reviewed-on: https://bazel-review.googlesource.com/#/c/7222
MOS_MIGRATED_REVID=138506715
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The simplest clock on Windows is timeGetTime(),
but its precision is ~15ms, which is not good
enough. This commit implements
blaze_util::WindowsClock that wraps a more precise
clock, accessible through QueryPerformanceCounter.
This change also deletes blaze_util_msvc.cc which
was recently forked off blaze_util_mingw.cc,
because forking didn't turn out to be necessary.
As part of this merging, I also renamed the file
to blaze_util_windows.cc
--
MOS_MIGRATED_REVID=138506308
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now flag_group can be marked with iterate_over field, that denotes for which
sequence variable the flag_group will be expanded repeatedly. This cl does that
in backwards compatible way as before, the iteration happened implicitly when the
used variable was found to be sequence at runtime. Because of that it adds some
extra code that will be removed once all the crosstools are migrated to the
explicit iteration.
--
MOS_MIGRATED_REVID=138501033
|
|
|
|
|
|
|
|
| |
- --client_debug that turns out debug logging from the client
- --connect_timeout_secs that controls the timeout of the initial Ping() RPC from the client to the server
--
MOS_MIGRATED_REVID=138491791
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Use proto_lang_toolchain() in java_proto_library, after fixing breakage.
Verified on Jenkins, http://ci.bazel.io/job/Gerrit-bazel-tests/169/
*** Original change description ***
Automated [] rollback of commit a396b070ae36032a973672e11145533621c39edc.
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138432193
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138417384
|
|
|
|
|
|
|
| |
'--legacy_expose_globs' flag has no effect now.
--
MOS_MIGRATED_REVID=138410651
|