| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
| |
When reporting about actions that are still running, groups those belonging
to the same test. In this way, more useful information can be presented in the
progress bar, instead of wasting a whole line for a single shard.
--
Change-Id: Id1f5a0595767906d6a75f6533be54f3c262ddd67
Reviewed-on: https://bazel-review.googlesource.com/#/c/3646
MOS_MIGRATED_REVID=123097744
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
killing of broken workers in the background, when no build is currently running, because we can only alert the user about what's going on while a build is currently running.
If you're a developer, this will probably help you when debugging a new worker.
Some messages you might see with --worker_verbose specified:
INFO: Worker configuration has changed, restarting worker pool...
WARNING: Javac worker (id 6) can no longer be used, because its files have changed on disk [13ce6c10546243b6b4ea2334dd3f8a55705e4c078cedd0e746d7ad7cee082e9a -> 9731223c50bab5c1f20d60d1a4967cf2726840727b6a639b6f6425547a9b4a10].
WARNING: Javac worker (id 4) can no longer be used, because its process terminated itself or got killed.
--
MOS_MIGRATED_REVID=123093071
|
|
|
|
|
|
|
| |
that belong to a prior running Bazel server.
--
MOS_MIGRATED_REVID=123092141
|
|
|
|
|
|
|
| |
Fixes #1300 .
--
MOS_MIGRATED_REVID=123090421
|
|
|
|
|
|
|
| |
path after we OOM, in an attempt to make that path complete more quickly and successfully.
--
MOS_MIGRATED_REVID=123040502
|
|
|
|
|
|
|
|
|
| |
pessimistically OOMing when GC thrashing. The first seems to make us hang on OOM, which is kind of the opposite of what we want.
These flags are now even more terribly named than they used to be, but a rename can wait until we actually know what we want.
--
MOS_MIGRATED_REVID=123036704
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=123035454
|
|
|
|
|
|
|
|
|
| |
//external package lookups, but keep the current (incorrect) semantics for unsuccessful //external package lookups.
Refactor some users of the old WorkspacePackageLookupValue.
--
MOS_MIGRATED_REVID=123034174
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=123026183
|
|
|
|
|
|
|
| |
around apple's buggy libtool tool
--
MOS_MIGRATED_REVID=123024674
|
|
|
|
|
|
|
| |
are not actually linked into test bundles.
--
MOS_MIGRATED_REVID=123021058
|
|
|
|
|
|
|
|
|
|
|
| |
Now that we batch-prefetch the nodes, there is no reason to delay this
check until the async Runnable runs, since we have more debugging
information this way.
--
Change-Id: Ic73d99ed8de184ba1e29f0dee5375f5d45b5379d
Reviewed-on: https://bazel-review.googlesource.com/3680
MOS_MIGRATED_REVID=123018542
|
|
|
|
|
|
|
|
|
|
| |
instead of passing and checking null in all helpers.
Demonstrates this pattern usage in a few select rules (e.g. AndroidBinary) where this was particularly egregious.
There are many places which can benefit from this pattern -- this change doesn't try to fix them all at once.
--
MOS_MIGRATED_REVID=123012378
|
|
|
|
|
|
|
|
|
|
| |
e.g. fail(3)
This is mostly useful for debugging (typical error messages will continue
to use strings).
--
MOS_MIGRATED_REVID=123008379
|
|
|
|
|
|
|
|
|
|
| |
The IDE doesn't add generated sources. Including these causes
execution of actions that generate sources, including building
whatever tools they need. This is not necessary for the IDE
stage.
--
MOS_MIGRATED_REVID=123004127
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122995313
|
|
|
|
|
|
|
|
|
| |
BlazeRuntime#getProductName() or a reference to TestConstants.PRODUCT_NAME for tests.
This CL prepares the codebase in order to delete the constant.
--
MOS_MIGRATED_REVID=122993568
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122988772
|
|
|
|
|
|
|
|
|
|
|
| |
commit 3fedf9e618cbce3dbdd00559b2de0bb8e2d43171 introduced the distinction between the loading phase and the workspace phase.
This check broke the use of native.existing_rule(s) in skylark remote repository, added a regression test for it.
Fixes #1277
--
MOS_MIGRATED_REVID=122988569
|
|
|
|
|
|
|
|
|
| |
targets that were added using addDeps(), instead of looking in the "deps" attribute.
This is currently a no-op, because collectTransitiveJavaSourceJars() is only called if noProviders() hasn't been called, which never happens in the current code in Blaze.
--
MOS_MIGRATED_REVID=122985812
|
|
|
|
|
|
|
| |
To use jars in deps, wrap them in java_import.
--
MOS_MIGRATED_REVID=122985072
|
|
|
|
|
|
|
|
|
| |
This prevents the case of a rule acquiring the null configuration in case the alias points to an input file. Which, in turn, makes "bazel build" work for these targets. The reason it breaks is that TargetCompletionValue instances are created from the associated ConfiguredTarget in SkyframeExecutor#buildArtifacts(), which means that if the configurations do not match, TargetCompletionFunction requests a different ConfiguredTargetValue than it was created from.
Fixes #1297.
--
MOS_MIGRATED_REVID=122973526
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122889821
|
|
|
|
|
|
|
|
|
| |
fragment was requested in the NullPointerException message.
This helps diagnose dynamic configuration errors.
--
MOS_MIGRATED_REVID=122855814
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122846987
|
|
|
|
|
|
|
|
|
| |
RuleClass is deserialized as part of a Skylark rule, the Environment is currently not present, but it is needed to detect changes to the rule.
Also precompute and store the Environment's hash code, and do a drive-by clean-up of a bunch of warnings in the Environment code.
--
MOS_MIGRATED_REVID=122838588
|
|
|
|
|
|
|
| |
allow for the exposure of values that are not typed as skylark primatives.
--
MOS_MIGRATED_REVID=122838580
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change allows starting remote worker with an embedded hazelcast server that listens to
a specific port. This allows test to run reliably.
Fixes #1271.
--
Change-Id: I0bb36af5837f83cad3d76b8acb50f89cd599ee87
Reviewed-on: https://bazel-review.googlesource.com/c/3650/
MOS_MIGRATED_REVID=122829898
|
|
|
|
|
|
|
|
|
|
|
|
| |
This required a few assorted changes:
- The FDO build stamp is not special-cased anymore, it is treated as a preprocessor define like any other.
- When compiling a .pcm file, use interfaceContext instead of the regular context when setting up the build variables. This is a bit more consistent and would be a good cause for a future bug.
This is a retry of commit 7841a6ab100fc35a67600f1ce1a70d293c51350e, which made some bold changes to LIPO that didn't work out well.
--
MOS_MIGRATED_REVID=122829825
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without this, old repositories are still cached across the change to
give a name in the WORKSPACE file, which results in annoying warnings.
This should have been included in
a7fea8a1467a89adde75e67bc99bf0e040f71fe9.
Fixes #1166.
--
Change-Id: I831b842dc07b4ca7925f003b68f4838d083b1166
Reviewed-on: https://bazel-review.googlesource.com/c/3660/
MOS_MIGRATED_REVID=122829553
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122825908
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122824226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
breaks []
*** Original change description ***
Move the command line arguments for C++ preprocessor defines to a feature.
This required a few assorted changes:
- The LIPO compilation context is not merged anymore. Include paths for auxiliary files are apparently taken from the profile files, so it is not necessary.
- The FDO build stamp is not special-cased anymore, it is treated as a preprocessor define like any other.
- When compiling a .pcm file, use interfaceContext instead of the regular context when setting up the build variables. Th...
***
--
MOS_MIGRATED_REVID=122823591
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a progress message has to be shortened, as it does not fit in a
line in the progress bar, add a new first attempt: if the message the
path implicit to the label, only shorten that path within the message
(if that gets short enough, leaving a reasonable part of the path);
usually, the additional information is more useful than having a longer
part of the path present.
While there, also fix incorrect length computation in a different case
of message shortening.
--
Change-Id: Ied80e03cace1b249fc0f4e11bce41f2b4207b6ad
Reviewed-on: https://bazel-review.googlesource.com/#/c/3670
MOS_MIGRATED_REVID=122818198
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122772973
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122772865
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122769355
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122755869
|
|
|
|
|
|
|
|
|
|
| |
to support cases like src/com/google/java, where the root is just src.
Also check for nested /src/ directories. This allows "blaze analyze"
to understand the classes provided by such "double src" rules and
match them up to java imports.
--
MOS_MIGRATED_REVID=122748028
|
|
|
|
|
|
|
| |
CLEANUP=<fixing documentation>
--
MOS_MIGRATED_REVID=122743083
|
|
|
|
|
|
|
| |
This fixed some fallout from commit 7894c18dbaf237a1c02d76beabe6ca54faf5039a. I also audited all the sites that change introduced ImmutableMap.Builder at.
--
MOS_MIGRATED_REVID=122738945
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollback of commit e37c55eccbd4516b2db7aaf58ef95209dfad3ed4 is complete so rolling this semantically unrelated change forward again
*** Original change description ***
Automated [] rollback of commit b8946eabd60a199a66a1892701d52d9801c7fb1a.
--
MOS_MIGRATED_REVID=122736257
|
|
|
|
|
|
|
| |
flags and environment variables.
--
MOS_MIGRATED_REVID=122735641
|
|
|
|
|
|
|
| |
ParameterFileWriteAction: Add support to write out CommandLine with tree artifact expansions.
--
MOS_MIGRATED_REVID=122734422
|
|
|
|
|
|
|
| |
ConfiguredTarget.
--
MOS_MIGRATED_REVID=122729392
|
|
|
|
|
|
|
|
|
|
|
| |
After the initial loading phase, further packages are loaded during
analysis. Show in the experimental UI the total number of packages
loaded during analysis phase to indicate at least some progress.
--
Change-Id: I345c6f806591e70e4397fc3e3365718dde95d7d2
Reviewed-on: https://bazel-review.googlesource.com/#/c/3645
MOS_MIGRATED_REVID=122728719
|
|
|
|
|
|
|
| |
RELNOTES: objc_framework now supports dynamic frameworks.
--
MOS_MIGRATED_REVID=122728042
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122727524
|
|
|
|
|
|
|
| |
Fixes #1290.
--
MOS_MIGRATED_REVID=122726071
|
|
|
|
|
|
|
|
|
|
|
| |
This required a few assorted changes:
- The LIPO compilation context is not merged anymore. Include paths for auxiliary files are apparently taken from the profile files, so it is not necessary.
- The FDO build stamp is not special-cased anymore, it is treated as a preprocessor define like any other.
- When compiling a .pcm file, use interfaceContext instead of the regular context when setting up the build variables. This is a bit more consistent and would be a good cause for a future bug.
--
MOS_MIGRATED_REVID=122725179
|