| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
When showing the earliest started actions in the progress
bar of the experimental UI, it is a wasted line to use a whole
line just to show dots indicating that more actions are running;
instead, just put the dots on the same line as the last action.
--
Change-Id: I37fcb654f689786ab522036b563409b15b85437f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3290
MOS_MIGRATED_REVID=119439830
|
|
|
|
|
|
|
| |
IOExceptions and so we need to check if any were encountered.
--
MOS_MIGRATED_REVID=119417412
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119369970
|
|
|
|
|
|
|
|
| |
We want sometimes to wrap them around a macro and make it impossible
to call them directly. So allow them to be private.
--
MOS_MIGRATED_REVID=119362967
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119361134
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119351752
|
|
|
|
|
|
|
|
|
| |
select a specific xcode.
RELNOTES: ios_device attribute "xcode", for declaring a specific xcode to use when selecting iOS simulators.
--
MOS_MIGRATED_REVID=119317344
|
|
|
|
|
|
|
|
|
| |
configuration.
This is useful for obtaining child split configurations and the information they provide.
--
MOS_MIGRATED_REVID=119295699
|
|
|
|
|
|
|
| |
packages from manifests. This prevents resources from being removed when they have been generated into a package other than the one specified in their target's manifest.
--
MOS_MIGRATED_REVID=119294591
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a less specific option specification in a rc file could override a more specific option specification when there's a non-trivial Command hierarchy. A concrete example would be a "build --foo=1" line overriding a "test --foo=2" line for a "test" invocation.
See the added test for more details.
Also fix some typos in BlazeCommandDispatcherRcoptionsTest.java.
Note that commit dc0fbb42ab22ab8f3205b0884069e1ffe03677c9 was rolled back in commit 417dad0f1e0d0ed4ccd5f8e52b49eb79937da49d which also incidentally rolled back commit 4f0fbe1b09333806cce76b75214e98c7684766e0. So this change is effectively a roll-forward of both of those, plus the bug fix, plus the typo fixes, and plus a documentation update.
--
MOS_MIGRATED_REVID=119276218
|
|
|
|
|
|
|
|
|
|
|
|
| |
Subscribe to the LoadingPhaseStartedEvent to get the LoadingProgressReceiver;
use it to provide information about the loading progress. As this event will not
be raised by the LegacyLoadingPhaseRunner, do not depend on this event and still
produce a sensible status bar if it is never raised.
--
Change-Id: I1db24ceaf7de4fc42d00b02f470066cb38c877b4
Reviewed-on: https://bazel-review.googlesource.com/#/c/3270
MOS_MIGRATED_REVID=119261675
|
|
|
|
|
|
|
| |
single else statement.
--
MOS_MIGRATED_REVID=119260729
|
|
|
|
|
|
|
|
|
|
|
| |
The main purpose of this event is to provide the LoadingProgressReceiver to
any interested listener. Note that this event will only be raised if the
option --experimental_skyframe_target_pattern_evaluator is given.
--
Change-Id: Ic675c9e1255b7d60de28bdad1ec1838655abd389
Reviewed-on: https://bazel-review.googlesource.com/#/c/3269
MOS_MIGRATED_REVID=119258070
|
|
|
|
|
|
|
|
|
|
| |
In this way, information about the progress of the loading phase
is collected.
--
Change-Id: I80ff0c91e27f0b55780c18c05fbb4fdda93263d3
Reviewed-on: https://bazel-review.googlesource.com/#/c/3268
MOS_MIGRATED_REVID=119255431
|
|
|
|
|
|
|
|
|
|
| |
Instances of this class keep track of the packages already loaded and those
currently being loaded. This information can be useful for UIs.
--
Change-Id: Ifd380dd2129d11181ad4a31ecbb71d142825df61
Reviewed-on: https://bazel-review.googlesource.com/#/c/3267
MOS_MIGRATED_REVID=119252784
|
|
|
|
|
|
|
| |
RELNOTES: implement list.insert for skylark rule
--
MOS_MIGRATED_REVID=119243427
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Changed the semantics of local .blazerc handling, requiring a Blaze release rollback ([]).
*** Original change description ***
Make specific options win over common ones
When specifying which command names to parse options for, given the
command annotation, ensure that "common" comes first, so that it can
be overridden by more specific options.
--
MOS_MIGRATED_REVID=119227260
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119224150
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119223631
|
|
|
|
|
|
|
| |
for adding support for NDK r11.
--
MOS_MIGRATED_REVID=119207577
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119203499
|
|
|
|
|
|
|
| |
This allows compilations with very long command lines to succeed.
--
MOS_MIGRATED_REVID=119199042
|
|
|
|
|
|
|
| |
proto-compiler use a params file.
--
MOS_MIGRATED_REVID=119193368
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119162307
|
|
|
|
|
|
|
|
|
| |
methods to return compiler options useful for reflection in aspects.
RELNOTES[NEW]: Objective-C compiler information is now available to Skylark.
--
MOS_MIGRATED_REVID=119160290
|
|
|
|
|
|
|
|
|
|
| |
Aspect becomes a triple (AspectClass, AspectDefinition,
AspectParameters) and loses its equals() method.
After this CL, SkylarkAspectClass.getDefintion still exists and is
deprecated.
--
MOS_MIGRATED_REVID=119159653
|
|
|
|
|
|
|
| |
It is only used for FDO, for which purpose it seems to be unnecessary.
--
MOS_MIGRATED_REVID=119151709
|
|
|
|
|
|
|
|
|
|
|
| |
SkyFunction.
This removes one of the two reasons for the existence of BuildConfiguration#prepareToBuild() which makes implementing dynamic configurations impossible and also makes FDO support halfway sane; now FDO is exactly as ugly as remote repositories, that is to say, reasonably okay.
Ideally, we'd implement the zip extraction as an Action and make it a TreeArtifact, but support for TreeArtifacts is not mature yet enough, so it's not possible at the moment.
--
MOS_MIGRATED_REVID=119150223
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
They were using "<ATTR>" which was parsed as a HTML tag.
ctx.file appeared as:
It is a shortcut for:
list(ctx.attr..files)[0]
ctx.files appeared as:
It is a shortcut for:
[f for t in ctx.attr. for f in t.files]
--
MOS_MIGRATED_REVID=119149347
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119141878
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This halves the overhead with sandboxing enabled vs disabled for a test
that basically only mounts a bunch of files out of a directory, and
slows that same test with a single extra file added to the directory
(but not mounted) by only ~4%.
The test is <https://gist.github.com/bsilver8192/10527a862ce16bb7f79a>
with 30000 inputs moved to a subdirectory and only 10 genrules.
This change means symlinks will be mounted directly as their target
rather than as a symlink, but this solves some weird behavior with
multi-level symlinks and will only break things which don't declare all
of their dependencies.
--
Change-Id: I1aa39dccb2e5fca2893bdab9065ee043d34019b2
Reviewed-on: https://bazel-review.googlesource.com/#/c/3220/
MOS_MIGRATED_REVID=119138157
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously AspectFunction was using an Aspect from the SkyKey, which
might have been stale.
This CL fixes the bug as uncovered in the test (see SkylarkAspectsTest),
but further refactoring is needed since SkylarkAspectClass equals() is
incorrect, and in fact obtaining the Skylark aspect definition should
always introduce Skyframe dependency.
--
MOS_MIGRATED_REVID=119137636
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1119
MOS_MIGRATED_REVID=119104941
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119104560
|
|
|
|
|
|
|
| |
when copying.
--
MOS_MIGRATED_REVID=119094214
|
|
|
|
|
|
|
| |
question, rather than during loading of the target's package. This way a target's package won't be in error if e.g. an unrelated target has empty 'srcs'.
--
MOS_MIGRATED_REVID=119079777
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119055012
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119053259
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119051781
|
|
|
|
|
|
|
| |
--
Change-Id: Ib83af0d0a04dc6b173bef1df28d17abc7a3c824d
Reviewed-on: https://bazel-review.googlesource.com/#/c/3120/
MOS_MIGRATED_REVID=119027507
|
|
|
|
|
|
|
|
| |
Resources in `java_library`s get the external repo path added to them, e.g., `foo` becomes `external/git_remote_repo/foo`. It needs to be removed, though I'm not sure this is the right way to strip it ...
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1085
MOS_MIGRATED_REVID=119024770
|
|
|
|
|
|
|
| |
Then less special-casing is needed and these files are always read by the compiler anyway, so we don't lose any incrementality.
--
MOS_MIGRATED_REVID=119023956
|
|
|
|
|
|
|
|
|
| |
building watch OS 1 apps.
RELNOTES: Support apple_watch1_extension and apple_watch_extension_binary rules for creating watch OS 1 extensions.
--
MOS_MIGRATED_REVID=119000703
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118969066
|
|
|
|
|
|
|
|
|
|
|
| |
android_binary (and java_binary).
RELNOTES[NEW]: The output of -printconfiguration of proguard is available
through an implicit "[target_name]_proguard.confg" output of android_binary (and
java_binary).
--
MOS_MIGRATED_REVID=118958246
|
|
|
|
|
|
|
| |
native rules to skylark rules and that returned from skylark rules to depending native rules. This fixes a bug where a skylark rule that did not touch the objc provider would automatically pass up the objc provider it received from dependencies to dependant native rules, leading to duplicate symbol linking errors when the same objc provider was exported twice.
--
MOS_MIGRATED_REVID=118947782
|
|
|
|
|
|
|
| |
names contain url, http or https.
--
MOS_MIGRATED_REVID=118946808
|
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, use progress events as an occasion to
update the progress bar. However, to avoid unnecessary noise, only
do so, if the progress bar potentially changes with time.
--
Change-Id: I9bee093c29e0eb50e7fcce2fa6e941a02d615def
Reviewed-on: https://bazel-review.googlesource.com/#/c/3206
MOS_MIGRATED_REVID=118944208
|
|
|
|
|
|
|
|
|
| |
1) Introducing the action_config message in the crosstool protobuf definition. The only part of that definition that are implemented in this CL is the "tool" section, other parts will be implemented in future CLs. The proto fields are here now to avoid being delayed by release cycles at each step of the implementation.
2) Refactoring the implementation of the "feature algebra" that computes the enabled features for a given toolchain. An interface called "CrosstoolActivatable" is used to represent any participant int the feature algebra, and can be either a feature or an action_config.
--
MOS_MIGRATED_REVID=118943663
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118943054
|