| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
This requirement was added to PatchTransition in commit e6392cd380fce14d719890c78d5eb2657e8a6cfc.
This also adds tests for ConfigFeatureFlagTransitionFactory's other
behaviors.
RELNOTES: None.
PiperOrigin-RevId: 158294134
|
|
|
|
|
|
| |
RELNOTES: ios_device and ios_test are deprecated. Please use the new testing
rules in https://github.com/bazelbuild/rules_apple instead.
PiperOrigin-RevId: 158290414
|
|
|
|
|
|
|
|
|
|
|
| |
companion project.
This depends on pull request #23 in bazelbuild/examples which uploads the required Java companion project.
Staged at []
RELNOTES: None.
PiperOrigin-RevId: 158287971
|
|
|
|
|
|
|
| |
indicative of the probable cause of the error.
RELNOTES: None.
PiperOrigin-RevId: 158286091
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 158279811
|
|
|
|
|
|
|
|
|
| |
When running bazel_windows_example_test, we don't need to add
--cpu=x64_windows_msys anymore, which means we can test the MSVC version
of Bazel in this test.
Change-Id: I01a2363e383756d57afd8beab20e66024612c8a0
PiperOrigin-RevId: 158279095
|
|
|
|
|
|
| |
previous change.
PiperOrigin-RevId: 158278265
|
|
|
|
|
|
|
| |
The underscore prefix is meaningful only for global variables (to make them package private).
RELNOTES: None.
PiperOrigin-RevId: 158277028
|
|
|
|
|
|
|
|
|
|
| |
if statements.
RELNOTES:
In .bzl files, top-level `if` statements are deprecated and will be forbidden
in the future. Move them in a function body instead (or use a conditional
expression instead: `x if condition else y`).
PiperOrigin-RevId: 158276986
|
|
|
|
|
|
|
| |
options.
Change-Id: If623f2416f8bff7c74ddf99d5c957a075de6494f
PiperOrigin-RevId: 158275892
|
| |
|
|
|
|
| |
PiperOrigin-RevId: 158267493
|
|
|
|
|
|
| |
This imports the new versions needed for #3030.
Change-Id: I82fc47c97acb96354fdeda1baf88ca06bd1e27cc
|
|
|
|
| |
Change-Id: I02463aacc17600918f6bae4e4065a88b6850de21
|
|
|
|
| |
Change-Id: Ifce1b51ef169ee8ac22fd90c0c68db3121b4296d
|
|
|
|
| |
Change-Id: I749fbbc8fa9565c2414452cc8e3708bad8a92f25
|
|
|
|
| |
Change-Id: Ic2969d328e211e3d977efeb2f778aceec1416a27
|
|
|
|
|
|
|
| |
The type was ignored, and it was expected that all expansion flags had
no value of their own, but was not checked.
PiperOrigin-RevId: 158261788
|
|
|
|
| |
PiperOrigin-RevId: 158256025
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will help diagnose
https://github.com/bazelbuild/bazel/issues/2977,
which I believed to have been fixed by the release
of 0.5.0, however it seems to have failed once
more with 0.5.0, alas without knowing the actual
bootstrap bazel's version I cannot be sure.
Change-Id: I71e100c549b4ef30699efe6363b72eb792ad1c23
PiperOrigin-RevId: 158243584
|
|
|
|
|
|
|
|
|
|
| |
Also add a helper method to GlobalVariables to
retrieve this path, thus concentrating the
assumptions about the layout of extracted_binaries
in one place.
Change-Id: If172b6f5bf4451845ad89d3d488ef2a2c2e5d286
PiperOrigin-RevId: 158241854
|
|
|
|
|
|
|
| |
- tag status results that are likely due to user behavior
- add a cache hit flag
PiperOrigin-RevId: 158240265
|
|
|
|
|
|
|
|
|
| |
An in-progress change will remove compiled R.java from runtime dependencies. To
make this file available to rules that depend on it it, expose it as an implicit
output instead.
RELNOTES: none
PiperOrigin-RevId: 158182310
|
|
|
|
|
|
|
| |
This is needed for migrating one of the internal crosstools
RELNOTES: None.
PiperOrigin-RevId: 158176295
|
|
|
|
|
|
| |
filesystem operations to check whether they've been written. In the common case, they haven't, and we can avoid checking that.
PiperOrigin-RevId: 158172182
|
|
|
|
|
| |
RELNOTES: n/na
PiperOrigin-RevId: 158162658
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks 1000+ targets in the depot: []
*** Original change description ***
Generate pre-reconciled ids R classes for dependency libraries with resources
in the transitive closure of robolectric tests.
RELNOTES: None
PiperOrigin-RevId: 158159550
|
|
|
|
| |
PiperOrigin-RevId: 158159054
|
|
|
|
|
|
| |
file" and "Bazel: Build Files and Terminology").
PiperOrigin-RevId: 158149353
|
|
|
|
|
|
|
|
|
| |
Additional changes:
- Introduce a Skylark macro java_library_srcs that provides the source jars of a java_*_library rule.
- Remove bazel's own java_proto_library implementation.
Change-Id: I18f2259bc75ca0fb32dcd8a6a857c609bd2c7773
PiperOrigin-RevId: 158146210
|
|
|
|
|
|
|
|
|
| |
Also adds a new target_platform attribute that checks the --cpu flag.
Part of #2219.
Change-Id: Icc732917db127ac8377a7722adc70b1a722d538a
PiperOrigin-RevId: 158143095
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the cygpath call on non-Windows platforms,
that was recently added by 102ce6ddc04063d26165c6a2167059f2348026bf
Also add a test for Bazel's Java launcher.
Also update the testenv.sh:cleanup method to wait
for Bazel to shut down, don't give up immediately
if it could not clean up the inner Bazel's temp
dir.
Fixes https://github.com/bazelbuild/bazel/issues/3092
See https://github.com/bazelbuild/bazel/issues/3069
Change-Id: I82b1026a60056f340caa53a59b6f2ec8a1397ef3
PiperOrigin-RevId: 158139846
|
|
|
|
|
|
|
| |
separate class. They're currently passed in around various callsites in the codebase and tests.
RELNOTES: None
PiperOrigin-RevId: 158139074
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
BlazeCommand.editOptions is currently called fairly late in the startup
process, so it must be restrictive in what it does, as any change to the
options can potentially introduce inconsistencies between different parts of
Bazel. Removing the CommandEnvironment reduces the amount of damage it can do,
and may allow us to move the call earlier in the startup process (maybe even
to a point where the CommandEnvironment does not exist yet).
PiperOrigin-RevId: 158133862
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fix for FreeBSD. I added the missing headers and verified that it now builds fine on FreeBSD 11, too.
*** Original change description ***
Automated g4 rollback of commit 7f520a8286c39c5145b6d816cd0be5a6b7b18250.
*** 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: 158133159
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 158131549
|
|
|
|
|
|
|
|
|
| |
- Only try to communicate with the server if it passes verification (i.e. the indicated PID exists and its start time is correct)
- Use only one thread to delete files on exit
- Don't set restart reason to NEW_VERSION unless there is an existing server
RELNOTES: None.
PiperOrigin-RevId: 158131470
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, it was in CoverageCommand, which led to all sorts of special casing
and workarounds, because it required options editing, error handling during
options editing, as well as early package path setup. It also caused us to
duplicate target pattern evaluation for the coverage command.
A semantic change is that the TestCommand can now also trigger the heuristic
instrumentation filter computation, if collect_code_coverage is enabled; we
might consider also enabling this for the BuildCommand, which can also have
collect_code_coverage enabled (e.g., when a user wants to build a non-test
binary with coverage instrumentation).
Also remove a bunch of unnecessary AbruptExitException declarations.
RELNOTES: bazel test now also computes a default instrumentation filter if --collect_code_coverage is enabled
PiperOrigin-RevId: 158129953
|
|
|
|
|
|
|
| |
These values are already used inside Google with specific semantics, so we
have to use these exact values (for now).
PiperOrigin-RevId: 158127273
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I likely broke that in 7f6e27f, although it was a pre-existing condition:
previously, the remote worker was reporting non-zero exit as a failure. Now it
reports the run as successful with a non-zero exit code. Update
RemoteSpawnStrategy to handle the exit code and generate an appropriate error.
In the future, we won't throw exceptions for non-zero exit at this level, but
instead report the non-zero exit in the SpawnResult, and have the caller
inspect that (and generate the error if applicable).
Fixes #3121.
Change-Id: Ia39f5c2ef5622544285c1957bb9ebae89e58edf2
Closes #3130.
Change-Id: Ia39f5c2ef5622544285c1957bb9ebae89e58edf2
PiperOrigin-RevId: 158120222
|
|
|
|
|
|
|
| |
Remove SpawnExecutionPolicy.shouldPrefetchInputsForLocalExecution in favor of
a static helper method in Spawns.
PiperOrigin-RevId: 158119993
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To enable a wrapper free MSVC CROSSTOOL,
set NO_MSVC_WRAPPER=1 or add --action_env=NO_MSVC_WRAPPER=1 flag.
Note that we still use windows_cc_wrapper.bat to invoke cl.exe
and link.exe for different actions.
Result for bazel build src/main/cpp:client :
NO_WRAPPER:
INFO: Elapsed time: 76.833s, Critical Path: 16.70s
WRAPPER:
INFO: Elapsed time: 138.517s, Critical Path: 27.78s
Change-Id: Iaf6b67fc791ae1f8b62d332e47f96f719510bda1
PiperOrigin-RevId: 158118110
|
|
|
|
|
|
|
|
| |
reading.
Closes #2794.
PiperOrigin-RevId: 158117701
|
|
|
|
|
|
| |
Also serves as an example for bug #3106.
PiperOrigin-RevId: 158116940
|
|
|
|
|
|
|
|
|
| |
It was previously the odd-one out in lib.analysis.actions, due to other code
that wanted to depend on it without pulling in all of analysis. However, it's
needed to interpret Spawn instances, and Spawn lives in lib.actions, so it
makes more sense to move it there, and remove the special-casing.
PiperOrigin-RevId: 158116684
|
|
|
|
|
|
|
|
|
|
| |
The help message previously said that `--batch` is strongly discouraged, but in fact it's only discouraged when using bazel interactively. Since the tradeoffs of `--batch` are fully explained in the online docs, this commit changes the help message to explain what the option does without getting into the tradeoffs.
Fixes #3051
Closes #3118.
PiperOrigin-RevId: 158112611
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ObjcProvider
This facilitates app->dylib->dylib dependencies, as the app needs to avoid linking in symbols
contained in any *transitive* dylibs, not just in any direct dylibs.
This also removes a test which verified the previous, incorrect functionality (not propagating
information about dylibs up the tree).
RELNOTES: None.
PiperOrigin-RevId: 158070381
|
|
|
|
|
|
|
| |
current rule name
RELNOTES: None.
PiperOrigin-RevId: 158068921
|