| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
already done, we should leave the thread in an interrupted state and proceed. This fixes a blaze crash when a 'genquery' execution is interrupted at the right time.
PiperOrigin-RevId: 157000269
|
|
|
|
|
|
|
| |
they were over-writable in all cases instead of differentiating by attribute type.
RELNOTES: None.
PiperOrigin-RevId: 156999284
|
|
|
|
|
|
| |
For #2409.
PiperOrigin-RevId: 156986600
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156983366
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156979845
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156979705
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156979038
|
|
|
|
|
|
|
| |
Currently sys_ioprio_set() is only implemented for Linux.
Change-Id: Iadacf8fd48a804b981274e92ca3066a403c467fb
PiperOrigin-RevId: 156977281
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, if the user has an SDK/NDK that is missing required directories, we
print out an InconsistentFileSystemException. This CL will give a better error,
indicating which directory is missing (or is not a directory).
Implementation is roughly taken from NewLocalRepositoryFunction.
Followup to https://github.com/bazelbuild/bazel/issues/2739.
RELNOTES: None
PiperOrigin-RevId: 156913532
|
|
|
|
|
|
|
| |
Removes references com.google.common.io.MoreFiles because it is not in //third_party/guava/guava-21.0-20161101.jar which we use for the JDK7 builds.
RELNOTES: None
PiperOrigin-RevId: 156912922
|
|
|
|
|
|
|
| |
The documentation for the current iteration of this feature is under android_sdk_repository.
RELNOTES: None
PiperOrigin-RevId: 156909364
|
|
|
|
|
|
|
| |
SkylarkType.Simple.
Change-Id: I7d6898bcba1689fee9e730b6134b659948501dae
PiperOrigin-RevId: 156903849
|
|
|
|
| |
PiperOrigin-RevId: 156896360
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward of directory name change
*** Original change description ***
Automated g4 rollback of commit 1d9e1ac90197b1d3d7b137ba3c1ada67bb9ba31b.
*** Reason for rollback ***
Breaks //src/test/shell/integration:force_delete_output_test
*** Original change description ***
Symlink output directories to the correct directory name
If the workspace directory is /path/to/my/proj and the name in the WORKSPACE
file is "floop", this will symlink the output directories to
output_base/execroot/floop instead of output_base/execroot/proj.
More prep for #1262, fixes #1681.
PiperOrigin-RevId: 156892980
|
|
|
|
|
|
|
|
|
|
|
| |
As it was suggested in
https://bazel-review.googlesource.com/#/c/10875/3/src/main/cpp/util/errors.cc@58
This is because that way it's consistent with the warnings/errors that the Bazel
server displays.
Change-Id: I65ee961ac4db5b21461fa7f7864e7f3c94a6e4f3
PiperOrigin-RevId: 156884812
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This broke Bazel CI on freebsd:
http://ci.bazel.io/view/Dashboard/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1516/console#
*** Original change description ***
Refactor process-wrapper code so the spawn/wait code is pluggable.
In an upcoming change I'll reintroduce the new platform-specific implementations that can kill and wait for all descendant processes spawned by the wrapped process.
This has no functional changes.
PiperOrigin-RevId: 156884488
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156876531
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
one.
This isn't a principled solution, but since it depends on /usr/bin/lcov, it should never be relied on at all. It's mostly a courtesy to people who came to use C++ coverage in Bazel before we removed it.
Fixes #2685.
Progress on #1118.
RELNOTES: None.
PiperOrigin-RevId: 156866370
|
|
|
|
|
|
|
|
|
| |
This includes some refactoring:
* Move the symbol deserialization our of the merger and into the ParsedAndroidData (probably move again.)
* Change the FailedFutureAggregator generics to work more callables
RELNOTES: None
PiperOrigin-RevId: 156863698
|
|
|
|
|
|
| |
Progress on #904.
PiperOrigin-RevId: 156862823
|
|
|
|
|
|
|
|
|
|
|
| |
action is present in extra actions attached to it.
Also rename cc_inc_library test to something that reflects better what it does (there was already a test case that did not have anything to do with cc_inc_library)
Fixes #2790 .
RELNOTES: None.
PiperOrigin-RevId: 156854584
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before CL 155913466, Desugar was not working when dumpDirectory was a relative path because of an extra/incorrect resolve() that ended up duplicating such a relative path.
CL 155913466 fixed this by converting Desugar's dumpDirectory to an absolute path. However, CL 156257767 introduced a check that Desugar's dumpDirectory must match the one in Java's InnerClassLambdaMetafactory, which broke the case of a relative path again.
Therefore, this CL undoes the conversion to absolute path again (so that Desugar's path matches that in InnerClassLambdaMetafactory). Instead, to make relative paths work, it drops the unnecessary/incorrect call to resolve().
A regression test is left for a future CL (I don't have a dev environment set up that would allow me to easily write one).
RELNOTES: None.
PiperOrigin-RevId: 156852882
|
|
|
|
|
|
|
|
| |
In an upcoming change I'll reintroduce the new platform-specific implementations that can kill and wait for all descendant processes spawned by the wrapped process.
This has no functional changes.
PiperOrigin-RevId: 156849610
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add an option allowing to set a hard limit on the number of characters
bazel will write to stdout/stderr (combined). In this way, it can be
avoided to overwhelm the user with information (especially, if the
invocation of bazel is wrapped in some way). Once the limit is approaching,
bazel will try hard to meaningfully reduce the output, but will ultimately
resort to just dropping output completely.
Change-Id: I49cce96cc6a025c9753632dd489021766df81077
PiperOrigin-RevId: 156849105
|
|
|
|
|
|
|
|
| |
While the fact that they are only added temporarily is obvious
from the comment, a machine-readable deprecation annotation is
more likely to be honored. So add it.
PiperOrigin-RevId: 156846712
|
|
|
|
|
|
|
| |
the same value.
RELNOTES: None.
PiperOrigin-RevId: 156837699
|
|
|
|
|
|
|
|
|
|
|
| |
advisable when overriding #equals().
Intricacies within Skyframe prevented us from adding this method before, but whatever those were are not a problem anymore. This was empirically proven by making the change, looking at the set of tests that failed when I last tried this, then finding that they don't fail.
The reason for the original failures will stay obscured by the mists of time forever.
RELNOTES: None.
PiperOrigin-RevId: 156835875
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156827893
|
|
|
|
|
|
|
| |
ctx.features has already merged the package-level and rule-level feature sets.
RELNOTES: None.
PiperOrigin-RevId: 156811464
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, we use Path.equals(Object), which will fail if we use
relative path in the system property. Now I use Files.isSameFile
which will check two paths point to the same file system
resource.
In https://github.com/bazelbuild/bazel/commit/69e855c7b0f0f7899a69a882cba0abd304233c97, I introduce the check to test whether setting
the system property for lambda meta factory succeeds. However,
the check does not consider relative path, which will always fail.
RELNOTES: n/a
PiperOrigin-RevId: 156796457
|
|
|
|
|
| |
RELNOTES: Using $(CC_FLAGS) in a GenRule adds a dependency to the c++ toolchain
PiperOrigin-RevId: 156770639
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156770067
|
|
|
|
|
|
|
| |
the default has been switched to "android".
RELNOTES: The 'legacy' Android manifest merger is deprecated. Please upgrade to the 'android' manifest merger, which is the same merger used by Gradle. https://developer.android.com/studio/build/manifest-merge.html
PiperOrigin-RevId: 156765307
|
|
|
|
|
|
| |
@loader_path/Frameworks rpath flag to the linker.
PiperOrigin-RevId: 156759162
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156747534
|
|
|
|
|
|
|
|
|
|
| |
For compiles that the CppConfiguration flags as needing PIC, the -fPIC
option needs to be added after the other compile options so that it cannot
be overridden (e.g. with a --copt). This is consistent with the way the
CppCompileAction compile options are ordered.
RELNOTES: None.
PiperOrigin-RevId: 156746218
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks android targets in the nightly - see []
*** Original change description ***
Do not retain transitive data in AndroidLocalTestBase.
The argument strings and artifacts were both transitive and flattened, causing O(N^2) memory consumption.
PiperOrigin-RevId: 156745610
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
java_library.exports and java_import.runtime_deps|exports|deps will now
accept any label from a rule that has a JavaProvider declared provider.
Note that java_library.deps|runtime_deps already had this feature and
this simply extends that privilege.
This relies on the fact that both those targets (via JavaCommon) are
simply searching for jars via JavaProvider anyway.
Added test for passing a custom Skylark rule (that provides a
JavaProvider) can successfully be added to the deps, runtime_deps, and
exports of java_library, java_import, and java_binary (where
appropriate).
Added integration tests for java_library.exports|runtime_deps (the basic
sandwich already tests deps) and java_import.exports|runtime_deps.
Note that custom Skylark rules are still unable to provide or propagate
a JavaNativeLibraryProvider, which results from a cc dependency. Also,
the deps argument for java_import is somewhat odd.
Change-Id: I7b2c19c6b99516ce524e8c82193d0c73e2d66530
PiperOrigin-RevId: 156740729
|
|
|
|
|
|
|
| |
separate method. This is so that android_local_test won't need access to the AndroidConfiguration fragment.
RELNOTES: None
PiperOrigin-RevId: 156740056
|
|
|
|
|
|
| |
If a target appeared in 2 different attributes, it is not processed twice, even if different aspects were applied to the different attributes. In that case, only one of the aspects is applied. This commit fixes this by checking which aspects have been applied to the target, instead of checking if the target was already processed.
PiperOrigin-RevId: 156738275
|
|
|
|
|
|
|
|
| |
And while at it cleanup all the calls of CppHelper.getToolchain and
CppHelper.getFdoSupport.
RELNOTES: None.
PiperOrigin-RevId: 156716291
|
|
|
|
|
|
|
|
|
| |
using multiple threads.
The immediate upside is that if multiple packages load the same bzl file, that file will only be read once when using loadPackages().
RELNOTES: None
PiperOrigin-RevId: 156621988
|
|
|
|
| |
PiperOrigin-RevId: 156589908
|
|
|
|
|
| |
RELNOTES: n/a
PiperOrigin-RevId: 156582965
|
|
|
|
|
|
|
|
| |
In both Python 2 and Python 3, the operator // is used for int division.
With Python 3, operator / is for float division.
RELNOTES: None.
PiperOrigin-RevId: 156582262
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156578239
|
|
|
|
| |
PiperOrigin-RevId: 156571671
|
|
|
|
|
|
| |
RELNOTES: Flag --explicit_jre_deps is now a noop.
PiperOrigin-RevId: 156570342
|
|
|
|
| |
PiperOrigin-RevId: 156558693
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the command line flags used by remote execution/caching as well as the
build event service (BES).
Major changes:
- Remote execution/caching and BES share flags for authentication and TLS.
- Removed API Key authentication from BES, as it's not being used.
- Add TLS support to BES upload.
- Add --bes_project_id flag. If set, the value is propagated as part of BES
lifecycle events.
For reviewers:
Start your review at CommonRemoteAndBesOptions, BuildEventServiceOptions and
RemoteOptions. The other changes are mostly automatic IDE renames of fields and
flag updates in shell script tests.
RELNOTES: None.
PiperOrigin-RevId: 156553857
|