| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
|
|
|
|
| |
recommended if there are no object files", when versioned shared library is in srcs fields like "a.so.2.0".
In appearsToHaveObjectFiles(), we take into account SHARED_LIBRARY, but no VERSIONED_SHARED_LIBRARY.
Fixes #310 .
--
MOS_MIGRATED_REVID=138408789
|
|
|
|
|
|
|
| |
RELNOTES: Comparing sets (`if set1 < set2:`) is not allowed anymore in Skylark because it didn't work correctly anyway.
--
MOS_MIGRATED_REVID=138408411
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138391269
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138387292
|
|
|
|
|
|
|
|
| |
away -- Bazel should still work with remote execution servers that don't have
that optimization.
--
MOS_MIGRATED_REVID=138384785
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously they returned nanoseconds but all call
sites converted those to milliseconds.
This is not only a simplification of the semantics
and renaming of the methods to make the returned
units and the purpose clear, but also preparation
for the Windows/MSVC implementations of these
methods.
--
MOS_MIGRATED_REVID=138383956
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For SpawnActions, depending on the value of use_default_shell_env,
the specified environment is taken. The shell environment, however,
consists of two parts: a static mapping of variables to values, and
a set of variables where the value is to be taken from the client
environment. Make sure, both parts are set correctly. Fixes #2035.
--
Change-Id: I32253e9bf651b18ca25107edc5fc839813905726
Reviewed-on: https://bazel-review.googlesource.com/#/c/7211
MOS_MIGRATED_REVID=138376914
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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=138372522
|
|
|
|
|
|
|
|
|
|
|
| |
context should generate a module map and module.
This whole code is a bit convoluted and the increasing number of boolean
parameters to initializeCppCompilationContext is smelly. I plan to clean this
up in a follow-up CL.
--
MOS_MIGRATED_REVID=138286169
|
|
|
|
|
|
|
| |
* This change removes forced -parse-as-library mode in favor of the driver figuring out how to parse each source. This means that main.swift will be parsed as a script and can contain top-level expressions.
--
MOS_MIGRATED_REVID=138285669
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138231767
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138223170
|
|
|
|
|
|
|
|
|
| |
documentation.
Fixes #1877.
--
MOS_MIGRATED_REVID=138199724
|
|
|
|
|
|
|
|
|
| |
This was an oversight on my part in the original implementation. As one
example, the Firebase AAR libraries contain AndroidManifest.xml's
with ${applicationId} and Google Play Services contain <meta-data> tags.
--
MOS_MIGRATED_REVID=138198047
|
|
|
|
|
|
|
| |
Add doc for the "read only" error message.
--
MOS_MIGRATED_REVID=138194709
|
|
|
|
|
|
|
| |
RELNOTES: Do not propagate aspect to its own attributes when using '*'.
--
MOS_MIGRATED_REVID=138194456
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change updates WindowsFileSystem so it:
- retrieves the DosFileAttributes instead of the
BasicFileAttributes, because the latter does not
report junctions as directories
- uses just isJunction to decide if a file is a
symlink, doesn't look at whether it's a
directory (again because java.nio.File also
incorrectly reports junctions as
non-directories)
Fixes https://github.com/bazelbuild/bazel/issues/1850
--
MOS_MIGRATED_REVID=138187220
|
|
|
|
|
|
|
| |
CompilationSupport.
--
MOS_MIGRATED_REVID=138185198
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138182982
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2025
--
MOS_MIGRATED_REVID=138181809
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138180229
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test was asserting that a proto message was
containing another one, by asserting string
containment. However on Windows the one method was
using CRLF line endings while the other was using
LF.
Fixes half of https://github.com/bazelbuild/bazel/issues/2025
--
MOS_MIGRATED_REVID=138175575
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138161512
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138143803
|
|
|
|
|
|
|
| |
that don't implement it.
--
MOS_MIGRATED_REVID=138126904
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138112581
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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=138109902
|