| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
Replace blaze_util::AsWindowsPathWithUncPrefix
with AsAbsoluteWindowsPath, which always returns
an absolute path.
Fixes https://github.com/bazelbuild/bazel/issues/2935
RELNOTES: none
PiperOrigin-RevId: 162727218
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this commit:
- remove blaze::PrintError in favor of
blaze_util::PrintError
- remove Ijar's PrintLastErrorMessage in favor of
blaze_util::PrintError
- use pdie every time path conversion fails,
because that indicates a fatal error (bad user
input for a path flag, or downright bug)
- remove explicitly printing GetLastErrror; pdie
and PrintError do it already
- unify the pdie/PrintError message formats
Fixes https://github.com/bazelbuild/bazel/issues/2935
Change-Id: I5feaf73885cab95c43a28c529ada6942e037b162
PiperOrigin-RevId: 162587490
|
|
|
|
|
|
| |
Close #3378.
Change-Id: I8ab58b00d5d8b86880c45f05feb139c01e0368aa
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 161785358
|
|
|
|
|
| |
Change-Id: Iaaf3272f45cce04d41e75ffbe2fa5b5b9f68734c
RELNOTES: None.
|
|
|
|
| |
Change-Id: I8b0f4e7547358704d038db312795c58acaaac4a7
|
|
|
|
|
|
| |
This reverts commit d82e69cef3f52f27c418c515f8af6af57d55aaf4.
This commit fails to build on Windows because of incorrect imports.
|
|
|
|
|
|
| |
The new version adds support for Python 3.
Change-Id: I88f322c6e9f35699fe5f708f52c5b84fb00a5b4b
|
|
|
|
|
|
|
|
|
|
| |
Please refer to patch set 9 and its CI run for usage and test
results. In practice, users should create their own java_toolchain
rule in their project's BUILD file, and set the two attributes like
above instead of modifying //tools/jdk/BUILD.
Change-Id: Ic880f243086b00a58d453a8139ba4c957fe54bc7
PiperOrigin-RevId: 159694649
|
|
|
|
|
|
| |
used wait_for_completion field.
Change-Id: I83a16d22f49c44989ec7030b5d2c9c9b1387e6e0
|
|
|
|
|
|
|
|
|
|
|
| |
This affects only the tuple that appears after 'if' inside a list
comprehension. Since a truth value is expected, it's very unlikely to break
existing code. It's technically a breaking change, but it's not worth
introducing a flag for this.
RELNOTES:
Parentheses around the tuple are now mandatory in [a for b in c if 1, 2]
PiperOrigin-RevId: 159218397
|
|
|
|
|
|
| |
This is part of https://bazel-review.googlesource.com/#/c/11590/.
Change-Id: Id4a7fd459013e3f25a5a99684ea04295e3b68fb4
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I recompiled the protobuf jars to be binary compatible with Java 6 by specifying -target 1.6 to javac.
Verified:
$ javap -v -cp third_party/protobuf/3.2.0/libprotobuf_java.jar com.google.protobuf.MessageOrBuilder | grep "major"
major version: 50
$ javap -v -cp third_party/protobuf/3.2.0/libprotobuf_java_util.jar com.google.protobuf.util.Durations | grep "major"
major version: 50
Change-Id: Ib40f8af8393de79dd431d08eb766c269bab2e608
|
|
|
|
|
|
| |
Close #3126
Change-Id: I457a215e147409d9449a3bca0bc0e88584f0ded5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is a follow-up to a recent change which allowed LLVM raw profile files
to be directly used with blaze. This change allows zipped LLVM raw profile
files.
This uses //tools/zip:zipper to extract the zipped file contents.
This also adds a new option to //tools/zip:zipper, 'j', to junk directories while
unzipping.
Tested:
blaze test //devtools/blaze/integration:fdo_test
blaze test //third_party/ijar/test:zip_test
RELNOTES[NEW]: Zipped LLVM profiles are now supported.
PiperOrigin-RevId: 158849516
|
|
|
| |
Use the print() function from future and use the "as" syntax for catching exceptions
|
|
|
|
|
|
| |
This fixes an exception being thrown and logged by the remote worker process
(//src/tools/remote_worker:remote_worker) every time the remote worker attempts
to access the remote REST cache.
|
|
|
|
|
|
|
|
| |
When bootstrapping, we generate a .zip file of generated java classes.
In this CL we add the java_library_srcs targets, that generate the
sources .jar files for bootstrapping.
Change-Id: Ib33edcc6ba996e433eb646a236e5f44c73b63460
|
|
|
|
|
|
| |
This imports the new versions needed for #3030.
Change-Id: I82fc47c97acb96354fdeda1baf88ca06bd1e27cc
|
|
|
|
| |
Change-Id: I02463aacc17600918f6bae4e4065a88b6850de21
|
|
|
|
| |
Change-Id: Ifce1b51ef169ee8ac22fd90c0c68db3121b4296d
|
|
|
|
| |
Change-Id: I749fbbc8fa9565c2414452cc8e3708bad8a92f25
|
|
|
|
| |
Change-Id: Ic2969d328e211e3d977efeb2f778aceec1416a27
|
|
|
|
| |
Change-Id: I580f519c1b274b497b3b37427a96e105bbe241dd
|
|
|
|
|
|
|
|
| |
Code taken from PR: https://github.com/grpc/grpc-java/pull/2975
Once this is merged into gRPC we can directly depend on gRPC.
Change-Id: Ide77414276b4125e85dfa6f93725143e3149d8ec
|
|
|
|
| |
Change-Id: I24e44ce87f5e042ddddb4cdbdcdd118a2d30a5eb
|
|
|
|
|
|
| |
the necessary targets depended upon by J2ObjCAspect.java.
Change-Id: I0a93378029707f0ebbda3a30b947519a385243f1
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add `https://github.com/googleapis/googleapis` as a third_party
dependency at commit `001f6702ac4cd72194a5120ff978fcfa740783d6`.
These protos are required for the upcoming open sourcing of the BES
protocol code.
Additionally, add (java_)proto_library() rules for the protobufs
required by the BES protocol.
Change-Id: Ie78a9941a62f2085a58ad859c91161885e6f390d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to use the build event service protobufs we need to support
protobufs well known types inside bazel. Unfortunately, due to a bug in
bazel's proto_library [1], protobuf can't provide such a proto_library
yet [2]. We expect this patch to be committed to protobuf upstream once
[1] is resolved.
Bazel's proto_library bug [1] is also the reason why this change has to
duplicate the well known protos under google/protobuf.
[1] https://github.com/bazelbuild/bazel/issues/2265
[2] https://github.com/google/protobuf/issues/2763
Change-Id: I5e16d437f2f581f11553049be0b4bcc564f4ad96
|
|
|
|
|
|
|
|
| |
1. Added config_settings for Windows
2. Don't use gcc warning options in copts, this made it possible
to build without python wrapper scripts.
Change-Id: I37521d717b9d2d488a3bb0ec658dad40c6ddbb27
|
|
|
|
| |
Change-Id: Iec9ded10a3a3c9562897090fcb7a1c01119676f7
|
|
|
|
| |
Change-Id: I4b9bddb695db15d6fe8113fb6d44518bc6909a17
|
|
|
|
|
|
| |
Fixes #2979
Change-Id: I23e38767e18a90b2262a38bf8f4b347e06d1de8d
|
|
|
|
|
|
| |
changes from https://github.com/google/protobuf/pull/2969 on top of it.
Change-Id: Ie49c5dcac06e370c5ab3863dc061513531ec8c0d
|
|
|
|
| |
Change-Id: If873b42945af0852a2b84261965655a5231e9f5f
|
|
|
|
|
|
|
|
|
|
| |
now that the upgrade is complete. The targets with suffixes were added
to make a two-step migration possible. Now that the migration is done
the suffix-less targets can provide the new versions, and the suffixed
targets can be directed to the un-suffixed targets until they are
removed.
Change-Id: I5632b14924df6a83a23e3f564d483f4925f72d08
|
|
|
|
|
|
|
|
| |
This patch was taken from [1] and fixes a CI breakage on Windows.
[1] https://github.com/google/protobuf/pull/2969/commits/14d2821157d047426c313759966d01f17b608c3a
Change-Id: Ibec9c3580566f573c7b558fffa40844da5239108
|
|
|
|
| |
Change-Id: Ifd865f0a14e7052ca40f0f9d52b5171de448734d
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969.
Change-Id: Id88cd7e5b2c27ab74f3ecfa1e127e5a863f2deb3
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/issues/2694
Change-Id: I33e1c1a6c1f1c4b31227eb26b0deed09525a7ec7
|
|
|
|
|
|
| |
This is the first part of a two-step migration to the new versions.
Change-Id: I3835b3db386f43cd00ca0d68c7fd2a42c3f9714f
|
|
|
|
|
|
|
|
| |
eventually be able to fix Android builds.
Progress on #2848.
Change-Id: I3b96425c2f5a4708629882e730d4907abd1226a6
|
|
|
|
| |
Change-Id: I468ab58151a6e62fa9d5d640142c38cd8886737b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It appears that jarjar is not actually used except for renaming classes
in the coverage collecting Java test runner as verified by
`find . -name BUILD | xargs grep jarjar`
Yak shaving for #2820.
This is necessary because the current version of jarjar does not work
with Java 8 classes because it embeds a version of ASM that doesn't
support that yet.
Change-Id: I6ac59b84bbbc1e85fe8e7f4f4876b98fc6129df0
|
|
|
|
|
|
|
|
|
| |
This is necessary for vendoring jarjar, which is in turn necessary to
get Java coverage collection to work again.
Yak shaving for #2820.
Change-Id: Idfd45e7322e0763fd316a4f67b1a048c93bf54ba
|
|
|
|
|
|
|
| |
This reverts commit 5235d06159ba6fee412bee261ea7867d061252b0.
Unfortunately, we noticed several build errors / test failures internally due this
change.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: Ic1daafe30270cb6bcc6231e6c94fb670af0475e7
|
|
|
|
| |
This reverts commit ea82aa115794b019472b44d4f94ed902c1217f30.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: I4f663955b0baeea3232b69ce32d9292427f5274a
|
|
|
|
|
|
|
| |
This is a prerequisite for the next javac update, and mirrors the
approach used for other javac-based tests in Bazel (e.g.
BazelJavaCompilerTest).
PiperOrigin-RevId: 152779250
|