| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118563271
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118561661
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118560010
|
|
|
|
|
|
|
| |
This is necessary because build-runfiles depends on the msys shared library, which (as per DLL lookup rules on Windows) is checked under the entries of PATH.
--
MOS_MIGRATED_REVID=118556684
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel http://ci.bazel.io/job/Bazel/417/JAVA_VERSION=1.8,PLATFORM_NAME=linux-x86_64/console
by using a Guava 20 feature, while Gauva 20 is not yet released.
*** Original change description ***
Set -fmodules-cache-path to be rooted in the genfiles directory whenever modules are enabled.
Also warn when -fmodules-cache-path is explicitly set by the user (either in configuration or rule attributes)
--
MOS_MIGRATED_REVID=118555994
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bazel clean never runs any actions, hence any message
about running actions would confuse the user. Therefore,
signal that clean is a non-building command so that the
experimental UI knows not the report about progress of
building.
--
Change-Id: I193f199b052e990992359bc9efdbe34db397ac5f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3125
MOS_MIGRATED_REVID=118554435
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118547283
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118525960
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118523482
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=118518790
|
|
|
|
|
|
|
| |
--objc_generate_debug_symbols. These are delivered in distinct files, with an architecture identifier.
--
MOS_MIGRATED_REVID=118510432
|
|
|
|
|
|
|
| |
RELNOTES: Restrict file types allowed for "strings" attribute to ".strings".
--
MOS_MIGRATED_REVID=118479031
|
|
|
|
|
|
|
|
|
| |
modules are enabled.
Also warn when -fmodules-cache-path is explicitly set by the user (either in configuration or rule attributes)
--
MOS_MIGRATED_REVID=118478856
|
|
|
|
|
|
|
|
| |
This is so that we can access the build options during creation, which is a
step towards making the coverage module stateless.
--
MOS_MIGRATED_REVID=118475354
|
|
|
|
|
|
|
| |
":extra_entitlements".
--
MOS_MIGRATED_REVID=118473605
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118473491
|
|
|
|
|
|
|
| |
This makes the late initialization of BuildView more obviously safe.
--
MOS_MIGRATED_REVID=118469655
|
|
|
|
|
|
|
| |
ConfigurationDistinguisher.EXTENSION to "IOS_APPLICATION" and "IOS_EXTENSION".
--
MOS_MIGRATED_REVID=118468650
|
|
|
|
|
|
|
| |
those modules already contain all the headers that are needed.
--
MOS_MIGRATED_REVID=118457691
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As explained in commit 37f3e9ee, after completion of the build, there
is no need any more to update the progress bar. Instead, its last line,
if any, can just float into the scroll-back buffer. From then on, STDOUT
and STDERR events are just passed through. Do so as well for any late
INFO, WARNING, or ERROR events. This will allow avoiding pointless
messages in commands like 'bazel clean' (the patch removing those messages
will also provide an appropriate integration test).
Unfortunately, to make this work properly, we must ensure that both
event handlers get informed about the fact that we have a no-build
command. To do this, we register the event handler with the intended
IO stream on the event bus, as well as a passively observing variant of the
event handler that has direct acces to the full output stream.
--
Change-Id: I148dc0065b6343e4a2a225b2d4fa615b4f720ff5
Reviewed-on: https://bazel-review.googlesource.com/#/c/3124
MOS_MIGRATED_REVID=118444275
|
|
|
|
|
|
|
| |
tests without binary_under_test
--
MOS_MIGRATED_REVID=118422688
|
|
|
|
|
|
|
|
|
| |
".plist"].
RELNOTES: Restrict file types used for "entitlements" attribute to [".entitlements", ".plist"]
--
MOS_MIGRATED_REVID=118416261
|
|
|
|
|
|
|
| |
non-keep-going build. Setting errorDepKey was only mostly harmless, to mix memes. (Actually, it was quite harmful.)
--
MOS_MIGRATED_REVID=118410594
|
|
|
|
|
|
|
|
|
| |
The lack of cc_library dependencies in generated Xcode projects can be worked around using _fully_linked.a and objc_import, but some include files still fail to propagate. In particular this affects genrule outputs and proto headers.
This fixes that issue.
--
MOS_MIGRATED_REVID=118397125
|
|
|
|
|
|
|
| |
instances by dependant objc_binary targets.
--
MOS_MIGRATED_REVID=118395529
|
|
|
|
|
|
|
| |
before)
--
MOS_MIGRATED_REVID=118394551
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118383557
|
|
|
|
|
|
|
|
|
| |
encountered during a build
Currently when evaluating a file or symlink leading to an external mutable object, Blaze throws an exception with unclear messages. The message does not contain the actual path but rather [/]/[] instead. This change updates FileFunction to allow bubbling up the error with the accurate path.
--
MOS_MIGRATED_REVID=118381323
|
|
|
|
| |
MOS_MIGRATED_REVID=118246740
|
|
|
|
|
|
|
| |
catastrophe. It doesn't add any logging information, and can mask the source of a crash if the crash has broken some invariants. <speculation>For instance, if we are crashing due to an OutOfMemoryError, the graph map may be in an inconsistent state where an attempt to add to it deleted a node</speculation>.
--
MOS_MIGRATED_REVID=118242401
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=118242131
|
|
|
|
|
|
|
| |
can trigger on it.
--
MOS_MIGRATED_REVID=118234431
|
|
|
|
|
|
|
|
|
| |
FileStateValues for output files can make their way into the Skyframe graph if a source file is symlink to an output file.
Also fix a bug where ExternalFilesHelper#isExternalFileSeen would always return true after returning true once in the past. This meant if an external file ever made its way into the Skyframe graph, we would always do a full graph scan at the beginning of each build (iow, we would always waste some CPU time doing nothing interesting).
--
MOS_MIGRATED_REVID=118190190
|
|
|
|
|
|
|
|
|
|
|
| |
This moves logic out of the Java repository function and closer to where it's
actually used, while also downplaying the basic templating a bit and allowing
the logic to interact better with the build file.
The existing logic regarding Apache's HTTP client is migrated as part of this.
--
MOS_MIGRATED_REVID=118084016
|
|
|
|
|
|
|
|
|
| |
and storyboards.
RELNOTES:
--
MOS_MIGRATED_REVID=118077315
|
|
|
|
|
|
|
| |
Fixes #545.
--
MOS_MIGRATED_REVID=118059971
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118049325
|
|
|
|
|
|
|
|
| |
This was causing javacopts containing '=' to be escaped, which makes them
invisible to the underlying javac invocation.
--
MOS_MIGRATED_REVID=118048317
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch replaces the usage of hardcoded "Blaze" string by
Constants.PRODUCT_NAME, so when presenting the output to the user
in the open source version, it says "Bazel" instead of "Blaze",
as "Blaze" is the internal name of the tool and "Bazel" the public
one.
Closes #842
--
Change-Id: I2917656d5254fe34b2761d6e2c79deef7c7fb8a5
Reviewed-on: https://bazel-review.googlesource.com/c/3103/
MOS_MIGRATED_REVID=118042541
|
|
|
|
|
|
|
| |
Fixes #1043
--
MOS_MIGRATED_REVID=118039426
|
|
|
|
|
|
|
|
|
|
|
| |
repository.download function now creates the necessary directories before
downloading.
Fixes #1069
Fixes #1078
--
MOS_MIGRATED_REVID=118026986
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118026638
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will tell the experimental UI not to produce updates on the
build status and also pass through correctly STDOUT/STDERR events.
In particular, the standard output is suitable for consumption by
other tools.
--
Change-Id: Ifffd445433a29df20f062a762fe6280229319196
Reviewed-on: https://bazel-review.googlesource.com/#/c/3123
MOS_MIGRATED_REVID=118024251
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118019851
|
|
|
|
|
|
|
|
|
| |
This both starts to clean up the code (making it clearer which platform each action is targeted to, caller by caller), as well as allows callers to issue
certain actions for platforms which are not implicitly ios.
We'll still need to migrate callers onto the new method signature.
--
MOS_MIGRATED_REVID=117982741
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117974145
|
|
|
|
|
|
|
| |
that keeps the Strings and creates the corresponding Value objects only at expansion time.
--
MOS_MIGRATED_REVID=117947058
|
|
|
|
|
|
|
| |
value 90. When --experimental_oom_more_eagerly is enabled, if after two full GCs the old gen is still >=--experimental_oom_more_eagerly_threshold% full, exit the JVM.
--
MOS_MIGRATED_REVID=117943361
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117939121
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, during build, STDOUT and STDERR events
are reported as separate events, properly terminated by CR LF.
After the completion of the build, however, STDOUT and STDERR
are passed through byte by byte, to allow nicely formatted output.
Info commands, however, do not build, so there is no event to signal
end of build; hence report that fact directly to the UI.
--
Change-Id: Ic236d33ee6e65637016370e15ed37e3d9494a258
Reviewed-on: https://bazel-review.googlesource.com/#/c/3122
MOS_MIGRATED_REVID=117934742
|