| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
wrapper objects: for OwnedArtifacts, which are the most numerous during builds, and for Labels for TransitiveTraversalValues, which are the most numerous during queries.
PiperOrigin-RevId: 154989520
|
|
|
|
|
|
| |
updates --experimental_one_version_enforcement from a boolean flag to a 3-state enum (OFF, WARNING, ERROR).
PiperOrigin-RevId: 154978203
|
|
|
|
|
|
|
|
|
| |
com.android.builder.internal
* Fixed formatting.
RELNOTES: None
PiperOrigin-RevId: 154973113
|
|
|
|
|
| |
Usage: --incompatible_depset_constructor=true (the default value is false).
PiperOrigin-RevId: 154971526
|
|
|
|
|
|
|
| |
to resolve classes hierarchy to determine whether a type is an exception type.
RELNOTES:n/a
PiperOrigin-RevId: 154971455
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Filter out conflicting flag policies for applicable commands. Only enforce the filtered, applicable policy.
*** Original change description ***
Automated g4 rollback of commit aa7f9307636d38cbb93a03acac8f4c59adfa0ee8.
*** Reason for rollback ***
Broke --experimental_inmemory_dotd_files
*** Original change description ***
Filter out conflicting flag policies before invocation policy enforcement.
This is to minimize the likelihood of obscure policy conflict. Now, the last policy on a flag (after policy expansion) will be the only one in the "canonical" invocation policy. There should be no reason for explicitly setting multiple policies on a single flag, but if an expansion flag is policy'd and one of its children has a more specific policy on it, make sure that the policy on the child flag is after the policy on the expansion flag.
Note that this restriction (only the last policy gets applied) also applies for repeatable flags. Make sure all values being set to a repeatable flag are set in a single SetValue operation, with multiple flagValues set.
PiperOrigin-RevId: 154969189
|
|
|
|
|
|
|
| |
Work towards #2880.
Change-Id: I7b661e368c0bd60fc6bcc10c7c1d63b82ba9702e
PiperOrigin-RevId: 154957882
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Otherwise they're read as HTML tags and "invisible." Oops.
PiperOrigin-RevId: 154956817
|
|
|
|
|
|
|
|
| |
Reorder definitions, based on user feedback.
Add some comments.
RELNOTES: None.
PiperOrigin-RevId: 154951404
|
|
|
|
|
|
|
|
|
| |
crosstool case.
To make the ios_framework_binary case to pass, the apple crosstool transition
needs to be applied to that rule.
PiperOrigin-RevId: 154949950
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The experiment did not succeed. It is valid for the fallback to succeed if
the original failure was due to a Strict Java Deps error, so enabling
this feature as it is currently implemented is not possible.
PiperOrigin-RevId: 154948042
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 154943665
|
|
|
|
|
|
|
|
| |
By recording registering a properly synchronized OutErr as listener
and providing it as OutErrProvider to the BuildEventStreamer.
Change-Id: Id553fcdb85327be28561634268511304fcc2ad3f
PiperOrigin-RevId: 154943162
|
|
|
|
|
|
|
|
|
| |
Almost every target has an OutputGroupProvider. Putting an
("output_groups", value) pair into SkylarkProviders creates an
unneccessary map. This CL removes it.
RELNOTES: None.
PiperOrigin-RevId: 154940624
|
|
|
|
|
|
|
|
| |
Almost every target has an OutputGroupProvider. Do not create another
Key->Provider map just for it.
RELNOTES: None.
PiperOrigin-RevId: 154937690
|
|
|
|
|
|
|
|
|
| |
Add flag to disable output of the runtime classes
necessary to support the try-with-resources feature
on older devices.
RELNOTES: n/a
PiperOrigin-RevId: 154933632
|
|
|
|
| |
PiperOrigin-RevId: 154931201
|
|
|
|
|
|
|
| |
no-op, and default behavior to on since it has been on in the global blazerc for awhile now.
RELNOTES: Deprecate use_singlejar_for_proguard_libraryjars and force behavior to always on.
PiperOrigin-RevId: 154890445
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 154877525
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling back the switch to rules_docker due to substantial performance regression in certain actions.
*** Original change description ***
Emit warnings when the bundled docker_build and docker_bundle rules are used.
PiperOrigin-RevId: 154869510
|
|
|
|
|
|
|
|
| |
Add static methods to return target kinds of InputFile and OutFile, as well as
suffix of target kind of Rule.
RELNOTES: None
PiperOrigin-RevId: 154866926
|
|
|
|
| |
PiperOrigin-RevId: 154860105
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This lets users specify that their test needs a minimum of <n> CPU cores
to run and not be flaky. Example for a reservation of 4 CPUs:
sh_test(
name = "test",
size = "large",
srcs = ["test.sh"],
tags = ["cpu:4"],
)
This could also be used by remote execution strategies to tune their
resource adjustment.
RELNOTES: You can increase the CPU reservation for tests by adding a "cpu:<n>" (e.g. "cpu:4" for four cores) tag to their rule in a BUILD file. This can be used if tests would otherwise overwhelm your system if there's too much parallelism.
PiperOrigin-RevId: 154856091
|
|
|
|
|
|
|
|
| |
Add an event reporting the workspace status as key-value pairs reported
via the workspace_status_command.
Change-Id: I5791551798a594bc2465f483eb97f9d4fd4c7cfd
PiperOrigin-RevId: 154845224
|
|
|
|
|
|
| |
--print-symbol-counts.
PiperOrigin-RevId: 154843561
|
|
|
|
|
| |
RELNOTES: 'output_groups' and 'instrumented_files' cannot be specified in DefaultInfo.
PiperOrigin-RevId: 154842022
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Original CL was rolled backed incorrectly. See post-submit discussion on http://https://github.com/bazelbuild/bazel/commit/7beadb7277453efec7e12b925005e7f0e003b592.
*** Original change description ***
Automated g4 rollback of commit 38b835097f9ae9a6062172b8a33ec2e2d1edde20.
*** Reason for rollback ***
Breaking Bazel build on linux, see http://ci.bazel.io/job/bazel-tests/733/
Repro: bazel build //src/test/java/com/google/devtools/build/lib:packages_test
Found by bisecting.
*** Original change description ***
Only allocate some formerly frequently allocated PathFragment objects once.
This reduces both gc churn and retained memory usage.
RELNOTES: None
PiperOrigin-RevId: 154839279
|
|
|
|
|
|
|
| |
as it corrupts its stdout
RELNOTES: None
PiperOrigin-RevId: 154838603
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 154836224
|
|
|
|
| |
PiperOrigin-RevId: 154835221
|
|
|
|
|
|
|
|
| |
The SpawnInputExpander can return null action inputs to indicate that we
should create an empty file at the corresponding location, without a
corresponding input file.
PiperOrigin-RevId: 154832564
|
|
|
|
|
|
| |
RELNOTES[INC]: objc_xcodeproj has been removed, use tulsi.bazel.build instead.
PiperOrigin-RevId: 154829733
|
|
|
|
|
|
|
| |
Work towards #2894.
RELNOTES: None.
PiperOrigin-RevId: 154829065
|
|
|
|
|
|
| |
Fixes #2924.
PiperOrigin-RevId: 154825240
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke rules_go and all its dependencies:
http://ci.bazel.io/job/rules_web/BAZEL_VERSION=HEAD,PLATFORM_NAME=darwin-x86_64/464/console
http://ci.bazel.io/job/rules_go/BAZEL_VERSION=HEAD,PLATFORM_NAME=darwin-x86_64/823/console
http://ci.bazel.io/job/buildifier/BAZEL_VERSION=HEAD,PLATFORM_NAME=darwin-x86_64/557/console
Bisected with `bazel build ...` in rules_go
The error message is still -whole-archive appearing in rules_go.
*** Original change description ***
Rollforward of: Basic open-source crosstool to support targeting apple platform types.
RELNOTES: None.
PiperOrigin-RevId: 154825240
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaking Bazel build on linux, see http://ci.bazel.io/job/bazel-tests/733/
Repro: bazel build //src/test/java/com/google/devtools/build/lib:packages_test
Found by bisecting.
*** Original change description ***
Only allocate some formerly frequently allocated PathFragment objects once.
This reduces both gc churn and retained memory usage.
RELNOTES: None
PiperOrigin-RevId: 154821457
|
|
|
|
|
|
| |
Closes #2866.
PiperOrigin-RevId: 154817470
|
|
|
|
|
| |
Change-Id: I32f6b16955ecefc242af8d9261418452d698c9ff
PiperOrigin-RevId: 154812955
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Extend the build-event streamer to also report about stdout/stderr,
if provided. This information is reported in the progress events. At
the moment, we only report stdout/stderr in progress events we send
anyway, but the interface is generic enough that we could add time-based
reporting later, if needed. Also note, that at the end of the build, we
report the final progress event, so that all stdout/stderr generated before
the build-complete event get also reported in the build-event protocol.
Change-Id: If5dbd59c151edbce02d0a9b2e5938b63c0a5dc58
PiperOrigin-RevId: 154811110
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without this change, any build using python3 and involving this tool fails with:
Traceback (most recent call last):
File ".../bazel-out/host/bin/external/bazel_tools/tools/build_defs/pkg/build_tar.runfiles/__main__/../bazel_tools/tools/build_defs/pkg/build_tar.py", line 22, in <module>
from tools.build_defs.pkg import archive
File ".../bazel-out/host/bin/external/bazel_tools/tools/build_defs/pkg/build_tar.runfiles/bazel_tools/tools/build_defs/pkg/archive.py", line 17, in <module>
from StringIO import StringIO
ModuleNotFoundError: No module named 'StringIO'
Closes #2865.
PiperOrigin-RevId: 154808860
|
|
|
|
|
|
| |
*** Reason for rollback ***
PiperOrigin-RevId: 154776438
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Relies on a CL that is being rolled back due to breaking some LIPO builds.
RELNOTES: None
PiperOrigin-RevId: 154776370
|
|
|
|
|
|
|
| |
The flag is still a no-op without --use_singlejar_apkbuilder.
RELNOTES: None
PiperOrigin-RevId: 154744739
|
|
|
|
| |
PiperOrigin-RevId: 154734540
|
|
|
|
|
|
| |
and fully linke actions.
PiperOrigin-RevId: 154733524
|