| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125376859
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125376554
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125368119
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125362963
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125360308
|
|
|
|
|
|
|
|
|
|
|
| |
nodes, where there is no work to do anyway.
This triggered some non-determinism that we explicitly workaround in the unit tests.
Also add a comment about a potential but unrelated optimization.
--
MOS_MIGRATED_REVID=125355303
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125354844
|
|
|
|
|
|
|
| |
Fixes #642.
--
MOS_MIGRATED_REVID=125351602
|
|
|
|
|
|
|
| |
Fixes #1314.
--
MOS_MIGRATED_REVID=125340361
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To keep the noise of messages in the scroll-back buffer low, limit
which test summaries are shown there.
- If a test fails to build, the error message about the build failure
is already in the scroll-back buffer---and more useful to the user
anyway.
- If a test is not run (either because the user interrupted the build,
or because of a build error), then either the user is aware of it
anyway or the information about the build failure is present and
more useful. Also, this is only detected at the end of the build,
were a summary of the tests is shown; hence avoid duplication here.
- If a test has status failed and there is precisely one failure log,
then the summary does not provide any useful information compared
to the individual FAIL message in the scrollback buffer.
While there, also show the precise status of the summary.
--
Change-Id: I13665db24f956c8d8b651dc38859649085b8bbcf
Reviewed-on: https://bazel-review.googlesource.com/#/c/3830
MOS_MIGRATED_REVID=125339810
|
|
|
|
|
|
|
| |
links.
--
MOS_MIGRATED_REVID=125336775
|
|
|
|
|
|
|
| |
Fixes #1333.
--
MOS_MIGRATED_REVID=125335174
|
|
|
|
|
|
|
| |
Part 1 of many for #1262, rolling forward.
--
MOS_MIGRATED_REVID=125334954
|
|
|
|
|
|
|
|
| |
a noticeable hotspot in profiles. (It would be even better if we could avoid
constructing this string until we actually need to produce an error message.)
--
MOS_MIGRATED_REVID=125323226
|
|
|
|
|
|
|
| |
(But this will make it easier to try out the overlayfs-based sandbox later.)
--
MOS_MIGRATED_REVID=125320914
|
|
|
|
|
|
|
|
|
|
| |
this is a noticeable hotspot in profiles of the loading phase.
(Every caller of lookup() or importSymbol() catches this and either
converts it to a non-exceptional condition or throws a new exception
which will have its own stack trace.)
--
MOS_MIGRATED_REVID=125320351
|
|
|
|
|
|
|
|
|
| |
Adds a runtime_deps attribute to compilation rules (including objc_binary) that imports a dynamic framework (generated either via the objc_framework or ios_framework rules) into an app bundle without linking against it at build time.
RELNOTES: objc_binary now supports late-loaded dynamic frameworks.
--
MOS_MIGRATED_REVID=125261347
|
|
|
|
|
|
|
| |
removed along with the per-order expander classes).
--
MOS_MIGRATED_REVID=125215096
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125188645
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125187340
|
|
|
|
|
|
|
| |
cc_fake_binary
--
MOS_MIGRATED_REVID=125187200
|
|
|
|
|
|
|
| |
passed-in modified file sets.
--
MOS_MIGRATED_REVID=125173579
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125171507
|
|
|
|
|
|
|
|
|
|
|
| |
args as a -filelist arg.
This prevents certain many-arg actions from making clang unhappy.
Also ensures that no -force_load artifacts are present in the filelist. Clang seems to not dedupe artifacts present in both a filelist and -force_load, causing duplicate symbol errors.
--
MOS_MIGRATED_REVID=125170226
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125166943
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Very often, when an action completes, a new one is started directly
afterwards. With this in mind, delay the refresh after the completion
of an action as long as acceptable by the refresh rate limiting. If
indeed an action starts within that time, we have replaced a double refresh
of the progress bar by a single one, thus make it appear less flickering.
--
Change-Id: I0e9143d6bba9929265ad2b6a3699486a1d5b3b2b
Reviewed-on: https://bazel-review.googlesource.com/#/c/3823
MOS_MIGRATED_REVID=125165516
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, for the running actions also report their strategy.
This will give a more complete picture of what Bazel is currently doing.
--
Change-Id: I9553c952ed494e0db225b2a1ae5e8eba00f68617
Reviewed-on: https://bazel-review.googlesource.com/#/c/3820
MOS_MIGRATED_REVID=125162808
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125160288
|
|
|
|
|
|
|
| |
This is to simplify the contract of BuildConfiguration.Fragment, thus making it simpler to create BuildConfigurations without unnecessary fragments and eventually create configuration fragments from Skylark.
--
MOS_MIGRATED_REVID=125137625
|
|
|
|
|
|
|
| |
describes the compilation, for use as is in another Java compilation.
--
MOS_MIGRATED_REVID=125128647
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
configuration creation fails because transitive fragment
visitation hits these cycles.
This makes CircularDependencyTest pass with dynamic
configurations.
It's a little bit unfortunate that BuildViewTestCase
follows a different code path to create configured targets
than production (BuildView.getConfiguredTargetForTesting
vs. BuildView.update). As a result, doing an actual build over
the rules defined in CircularDependencyTest#testTwoCycles
correctly reports the cycle, while the test itself doesn't.
That means the test isn't 100% faithfully testing production
logic.
But I'm not interested in fixing the gap between
BuildView.update and BuildView.getConfiguredTargetForTesting
in this change. That's part of a larger refactoring effort
on the various forked ways of acccessing configured targets
and dependencies in BuildView.
--
MOS_MIGRATED_REVID=125118553
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
repositories
One interesting side effect of how this is implemented is that for external
repositories, bin/ and genfiles/ are combined. External repo output is under
bazel-out/local-fastbuild/repo_name for each repo.
Fixes #1262.
RELNOTES[INC]: Previously, an external repository would be symlinked into the
execution root at execroot/local_repo/external/remote_repo. This changes it to
be at execroot/remote_repo. This may break genrules/Skylark actions that
hardcode execution root paths. If this causes breakages for you, ensure that
genrules are using $(location :target) to access files and Skylark rules are
using http://bazel.io/docs/skylark/lib/File.html's path, dirname, etc.
functions.
--
MOS_MIGRATED_REVID=125095799
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks some builds, e.g. googlemac/iPhone/Applecrisp/Shared/DocosLib:DocosLib
*** Original change description ***
When building ObjectiveC++, pass the flag -std=c++11 in addition to -stdlib=libc++.
RELNOTES: When building ObjectiveC++, pass the flag -std=c++11 in addition to -stdlib=libc++.
--
MOS_MIGRATED_REVID=125095396
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, another 5 java_test targets of Bazel passed on Windows:
//src/test/java/com/google/devtools/...
build/lib/bazel/repository/downloader:DownloaderTests
build/lib:graph_test
build/lib:java-rules-tests
build/lib:profiler-tests
build/lib:windows_test
Already passing targets are:
//src/test/java/com/google/devtools/...
build/android/ziputils:ziputils-tests
build/lib:BazelDocumentationTests
build/lib:objc-rules-tests
build/skyframe:skyframe_base_test
common/options:options_test
--
Change-Id: Ibb63f29615b84d6df44289c902f6d85ab6569d61
Reviewed-on: https://bazel-review.googlesource.com/#/c/3821
MOS_MIGRATED_REVID=125084737
|
|
|
|
|
|
|
| |
Previously we were interspersing these doubly, resulting in constructs like "-F -F -F FrameworkPath"
--
MOS_MIGRATED_REVID=125071017
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Local repositories were not marked, so if a WS file switched from
remote->local->remote, on the first run the remote rule would create a mark
file, on the second run the local rule would ignore it, and then on the third
run the remote rule would look at the mark file and see, "I'm already
up-to-date," leaving the repository as a local repo.
Fixes #977.
--
MOS_MIGRATED_REVID=125060180
|
|
|
|
| |
MOS_MIGRATED_REVID=125042781
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pass the executionInfo available from a action argument to
Spawn{Gcc,Link}Strategy execution methods. This change makes
execution_requirements specified in CROSSTOOL effective at tool
execution time for compilations and links.
--
Change-Id: I92a6a9c6b19224756f0adb31673cddca94cfe658
Reviewed-on: https://bazel-review.googlesource.com/3760
MOS_MIGRATED_REVID=125041898
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125013752
|
|
|
|
|
|
|
|
|
|
|
| |
keep_going is turned on
Current implementation only supports custom exit code from {@link
ActionExecutionException} in fail-fast mode. This change allows appropriate
error code to be returned based on all reported errors during build phase.
--
MOS_MIGRATED_REVID=124987173
|
|
|
|
|
|
|
| |
potentially-relevant options from the creation of the callback.
--
MOS_MIGRATED_REVID=124981132
|
|
|
|
|
|
|
|
|
| |
This builds all dependencies linked against watch SDKs instead of iOS SDKs, and builds for the architectures specified in --watchos_multi_cpus
RELNOTES: apple_binary supports a new platform_type attribute, which, if set to "watchos", will build dependencies for Apple's watchOS2.
--
MOS_MIGRATED_REVID=124980029
|
|
|
|
|
|
|
| |
the default value of a parameterized aspect attribute is null. This is hypothetical because I couldn't figure out an end-to-end way to tickle the bug. Still, the surrounding code is very brittle and things may change in the future such that the bug is trivially tickle-able.
--
MOS_MIGRATED_REVID=124977450
|
|
|
|
|
|
|
| |
Also add platform sdk versions to the build variables defined by AppleCcToolchain, so that these values may be referenced in crosstool config.
--
MOS_MIGRATED_REVID=124976362
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124975604
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124968182
|
|
|
|
|
|
|
| |
values arise when a None is used as the value of a Selector for a type without a default value.
--
MOS_MIGRATED_REVID=124961388
|
|
|
|
|
|
|
| |
use_objc_header_names attribute.
--
MOS_MIGRATED_REVID=124955824
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124951254
|
|
|
|
|
|
|
| |
It was not used (IIRC the last user was FdoSupport while it lived inside CppConfiguration)
--
MOS_MIGRATED_REVID=124938836
|