| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the progress bar cannot be updated in place, every additional writing
of the progress bar clutters up the log. Of course, this could be controlled
by adding --show_progress_rate_limit or even --noshow_progress options to the
invocation; however, it turns out that users expect a bazel to just automatically
reduce its output rate. Therefore, specify a minimal value for the progress rate
limit of 2 seconds if the progress bar cannot be updated in place. Also, increase
the time rate for purely time-based updates to 20s in this case.
Moreover, only automatically redraw the progress bar after an INFO/WARNING/... message,
if it can be updated in place.
--
Change-Id: I7d06aa04acec457ec0a5d20ac32ede4cf80f7170
Reviewed-on: https://bazel-review.googlesource.com/#/c/3944
MOS_MIGRATED_REVID=126387987
|
|
|
|
|
|
|
| |
Android split transitions.
--
MOS_MIGRATED_REVID=126378169
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126375064
|
|
|
|
|
|
|
|
|
|
|
|
| |
This warning is printed on every invocation, and the visual noise helps blind
the user to other more imporant warnings. Presumably they have chosen to set
--jobs high for a reason. Help them make a good choice with the documentation,
then don't distract them further.
RELNOTES: Remove warning for high value of --jobs.
--
MOS_MIGRATED_REVID=126369509
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126344189
|
|
|
|
|
|
|
|
|
|
|
| |
blaze handling.
- Converted to correct upstreamed options
- Handling of bitcode when creating dynamic libraries
- New LTOBackendAction derived from SpawnAction that discovers and adds the imported bitcode files identified by the LTO indexing step.
--
MOS_MIGRATED_REVID=126344132
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126333303
|
|
|
|
|
|
|
|
| |
(2) Refactor the simple query concurrency support by introducing QueryExpression#canEvalConcurrently and removing the primitive BinaryOperatorExpression#evalConcurrently and the hardcoded SkyQueryEnvironment logic around it. This way each QueryExpression can safely manage its own concurrency. A followup CL will ensure that concurrent evaluation occurs for as much of the query expression as possible, rather than just for the top-level query expression node.
(3) Make a few query internals public.
--
MOS_MIGRATED_REVID=126324637
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126310706
|
|
|
|
|
|
|
| |
sane Java API for now)
--
MOS_MIGRATED_REVID=126306559
|
|
|
|
|
|
|
|
| |
These don't do anything for a 64-bit JVM.
Also remove some very old GC tuning flags for --batch.
--
MOS_MIGRATED_REVID=126303269
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add .dll as a shared library type like .so
If we have target:
cc_binary(
name = "bar.dll",
srcs = ["bar.cc"],
linkshared = 1,
)
Now we can build a dll using bazel build //foo:bar.dll
If the target name is still bar.so, the wrapper script also
build the dll by copying the output file to bar.dll.
--
Change-Id: Ie3d1fb83965ddf691d0cc4734a61a0b0ce89d948
Reviewed-on: https://bazel-review.googlesource.com/#/c/3931
MOS_MIGRATED_REVID=126301390
|
|
|
|
|
|
|
| |
This way it won't print if the repo maintainer doesn't set the repo name.
--
MOS_MIGRATED_REVID=126300205
|
|
|
|
|
|
|
| |
attributes as their parameters (instead of using an attribute map).
--
MOS_MIGRATED_REVID=126298988
|
|
|
|
|
|
|
|
|
|
|
| |
Also, the number of pending items seems to 'leak' and always increase.
Be sure to add each package only once, even if the computation has to be restarted.
RELNOTES: The progress message would not clear packages that need to be loaded twice.
--
MOS_MIGRATED_REVID=126295556
|
|
|
|
|
|
|
|
|
| |
that's what it does.
In particular, it affects Windows.
--
MOS_MIGRATED_REVID=126293339
|
|
|
|
|
|
|
|
|
|
|
| |
If this is set to true (which it is by default), JavaCompilationHelper will set the "supports-workers" tag on the execution info for the Javac SpawnAction. If it is explicitly set to false, this tag will be absent.
In a follow-up CL, the WorkerSpawnStrategy will check whether this tag is present and fallback to non-worker execution if not.
This is needed to safely enable workers by default in Bazel without breaking the older JDK7 JavaBuilder, which does not support workers yet.
--
MOS_MIGRATED_REVID=126290991
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ExperimentalEventHandler uses no functionality of BlazeCommandEventHandler,
hence there really is no need whatsoever for ExperimentalEventHandler to be
a subclass of BlazeCommandEventHandler. So, remove this inheritance to clean
up our class hierarchy; instead let the ExperimentalEventHandler just implement
the EventHandler interface.
--
Change-Id: I504f727190a12882dd8b7c37811a821e3ba50400
Reviewed-on: https://bazel-review.googlesource.com/#/c/3926
MOS_MIGRATED_REVID=126282974
|
|
|
|
|
|
|
| |
The first option was renamed to --java_deps, and the second was a no-op.
--
MOS_MIGRATED_REVID=126280008
|
|
|
|
|
|
|
|
|
| |
"supports-workers" execution info tag.
This is a new requirement which helps Blaze decide whether an action can be executed via workers or not.
--
MOS_MIGRATED_REVID=126279864
|
|
|
|
|
|
|
| |
every process wrapper again.
--
MOS_MIGRATED_REVID=126279021
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126275468
|
|
|
|
|
|
|
| |
Previously, the command-line reference page put a line break between them.
--
MOS_MIGRATED_REVID=126274327
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
legacy_native_support makes it so that Bazel copies .so's instead of linking.
This allows Bazel to include third-party native code without running an NDK.
Turning it off allows Bazel to actually compile native code, but at the cost
of this copy case no longer working without an NDK, and creating an unnecessary
shared library which will most likely never be used.
This CL makes it so that if no actual source code or static libraries are
in the transitive closure, the linker is not run at the android_binary level.
This means that legacy_native_support as a separate concept can be removed,
and it is - the attribute remains, but is a no-op. This will be removed in
a future change. The matching flag (--legacy_android_native_support) has
already been removed.
RELNOTES: The link mode for Android native code is now automatically determined
based on the transitive closure of cc_libraries, and legacy_native_support is
now a no-op. --legacy_android_native_support has been removed.
--
MOS_MIGRATED_REVID=126244755
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126215213
|
|
|
|
|
|
|
| |
experimental_objc_library.
--
MOS_MIGRATED_REVID=126204758
|
|
|
|
|
|
|
| |
this and commit 116c2f6724718fc408e0c73c9026d89281c75e87 using Guava's Ascii#truncate.
--
MOS_MIGRATED_REVID=126198762
|
|
|
|
|
|
|
| |
looking at the declared include srcs of all transitive deps was sufficient as these contained all headers possibly relevant even with LIPO optimizations. With interface deps, we cut off dependencies (and thus headers) that aren't directly includable. To still make those available to LIPO, we need to also supply the declared include sources coming from lipo scannables.
--
MOS_MIGRATED_REVID=126183112
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes the event reporting the completion of the last action
can, effectively, overtake the event reporting the completion of
last action. To avoid late writing to the output stream don't start
the update thread after the completion of the build is reported.
There is nothing to update then any more anyway.
--
Change-Id: Ibbb6d025635a9daa233c2b28ca64a1ae4896ce47
Reviewed-on: https://bazel-review.googlesource.com/#/c/3922
MOS_MIGRATED_REVID=126182576
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126177747
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, if a build completes with tests failing, the final status
message is "INFO: Build completed successfully, xxx actions". While
technically correct, it might mislead the user to believing all tests
have passed (especially when only looking at the status in the terminal
title). Therefore, if a build completes with failing tests, mention the
number of failed tests in the final status message.
--
Change-Id: I9234fbfdf2ad43dd29af660966dde73bf0c9311a
Reviewed-on: https://bazel-review.googlesource.com/#/c/3918
MOS_MIGRATED_REVID=126176452
|
|
|
|
|
|
|
|
|
| |
Previously we used labels in each configuration fragment that then got added to every test action. Instead, we now have a filegroup under //tools/test for coverage files that truly need to be on the inputs of every test action and collect language-specific support files in InstrumentedFilesProvider.
This makes configuration creation simpler and makes it possible to turn --crosstool_top into something else other than a filegroup (previously, it was that filegroup that got added to every test action)
--
MOS_MIGRATED_REVID=126170241
|
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, also support the --show_timestamps option
which asks that for each event a timestamp be added to the the
output. Fixes #1436.
--
Change-Id: I8f9db958525edfbca12ed2c1f1396f25f865b897
Reviewed-on: https://bazel-review.googlesource.com/#/c/3916
MOS_MIGRATED_REVID=126165328
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126161513
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This attribute marks annotation processors that generate API code.
If a rule uses an API-generating annotation processor, other rules depending on
it can refer to the generated code only if their compilation actions are
scheduled after the generating rule.
In the future, annotation processors will only be considered by header
compilation if they set generates_api=1.
--
MOS_MIGRATED_REVID=126152384
|
|
|
|
|
|
|
| |
InvalidatedNodeEntry.
--
MOS_MIGRATED_REVID=126139179
|
|
|
|
|
|
|
|
|
| |
error-free built-in rules, and to non-rules. This should save memory, as well as CPU for built-in rules, since we don't have to make sets out of their providers more than once.
Also fix a bug in the equality check where we weren't comparing the canHaveAnyProvider field properly.
--
MOS_MIGRATED_REVID=126121351
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126120891
|
|
|
|
|
|
|
|
|
| |
versions, even if no --xcode_version is specified.
it also avoids throwing an exception if an xcode_version is aliased to its proper name, to be a bit more lenient.
--
MOS_MIGRATED_REVID=126120071
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126104957
|
|
|
|
|
|
|
| |
they actually return a Path and not a File.
--
MOS_MIGRATED_REVID=126102820
|
|
|
|
|
|
|
| |
repository_ctx.execute, so that it allows overriding current environment variables
--
MOS_MIGRATED_REVID=126089693
|
|
|
|
|
|
|
| |
--
Change-Id: I88c67ba382288f0a908aba97571564434eaae2d0
Reviewed-on: https://bazel-review.googlesource.com/#/c/3917
MOS_MIGRATED_REVID=126085117
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126081020
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126079533
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126076585
|
|
|
|
|
|
|
| |
don't perform internal sanity checks.
--
MOS_MIGRATED_REVID=126073693
|
|
|
|
|
|
|
|
|
| |
This is the first actual use of Windows JNI!
Also a cleanup of ProcessUtils. Injecting a mock implementation was never used.
--
MOS_MIGRATED_REVID=126068832
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126068553
|
|
|
|
|
|
|
|
|
|
|
|
| |
When writing the experimental state tracker is asked to produce a progress
bar, it can be requested to have a one-line version. This one is used, e.g.,
if curses are not available and therefore it cannot be erased. Also honor
that request, if reporting about loading progress.
--
Change-Id: Ice3045fc86280e420b789a94b03427ff578f4a11
Reviewed-on: https://bazel-review.googlesource.com/#/c/3912
MOS_MIGRATED_REVID=126057511
|