| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
but due to the flag default value being true, some code behaved as if it was).
--
MOS_MIGRATED_REVID=99913146
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99904596
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To allow the commands in the cc_fake_binary to work with modules (which is
a precondition to writing nocompile tests for modules), we need to create
header modules in the same pic/nopic mode as the rest of the commandline
indicates.
There are two ways to resolve this problem:
a) Make cc_fake_binary use the same pic mode as other binaries.
b) Make sure fake compile actions get all their inputs in non-pic mode.
This patch proposes solution a), as that makes sure cc_fake_binary is as close
to the actual compilation going on as possible; for example, if we decide to
always use pic in the future, this will simply work; additionally, we will
currently get more test coverage through different compilation modes.
RELNOTES: 'cc_fake_binary' uses the same pic/nopic mode as other binaries.
--
MOS_MIGRATED_REVID=99902738
|
|
|
|
|
|
|
|
|
| |
flag'-DDEBUG=1' to 'fastbuild' for objc.
RELNOTES: Make '-DDEBUG=1' available for objc fastbuild via --experimental_allow_fastbuild_debug
--
MOS_MIGRATED_REVID=99896083
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99867246
|
|
|
|
|
|
|
| |
This isn't really a crash, so don't report a crash, just log locally and remotely.
--
MOS_MIGRATED_REVID=99857034
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99852261
|
|
|
|
|
|
|
|
|
| |
non-pattern sub-expressions via file stat or directory listing.
There is an inherent incrementality tradeoff here: A directory listing should be independent of any file edits in the directory, but may be overly conservative if an unrelated file is added or removed. The file stat is overly conservative when the file is modified, since glob() cares only about existence vs. non-existence.
--
MOS_MIGRATED_REVID=99838654
|
|
|
|
|
|
|
|
|
| |
- Objects of different types can now be compared.
- Printer now prints dictionaries in a deterministic order, even when the keys have different types.
- testEval() in EvaluationTestCases evaluates both expressions instead of comparing expression strings. Consequently, if a statement describes a collection, its order does no longer matter when doing the comparison.
--
MOS_MIGRATED_REVID=99829458
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99828091
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99823918
|
|
|
|
|
|
|
|
| |
The content is checked for determinism using SHA-256 sum. Following
redirection allows for using mirror based service.
--
MOS_MIGRATED_REVID=99819904
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99819719
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99813196
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99804135
|
|
|
|
|
|
|
| |
indicates an error, and tests shouldn't normally have such errors.
--
MOS_MIGRATED_REVID=99789434
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99775681
|
|
|
|
|
|
|
|
|
| |
color when the build fails.
Includes fix for problems causing the original slowdown to blaze query
--
MOS_MIGRATED_REVID=99755414
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99747336
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaking builds. []
*** Original change description ***
RELNOTES: actoolzip, momczip and swiftstdlibtoolzip have all been made into bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change.
--
MOS_MIGRATED_REVID=99742398
|
|
|
|
|
|
|
|
|
| |
we should now fail the test if there's an exception thrown in a worker thread that would cause a deadlock due to countdown latches not being mutated as expected.
I don't know why the Mac Bazel tests are internally failing to build. Any ideas? I was very cargo-culty with the testutil library because I have no idea what's going on there with the duplicate packages.
--
MOS_MIGRATED_REVID=99733410
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99720083
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99718820
|
|
|
|
|
|
|
|
|
|
| |
Don't compute the linkopts in CcCommon unconditionally, only on demand. In
order to only do this once, I had to pull out all calls to getLinkopts and
move them up in the call hierarchy. This in turn resulted in some
simplification and dead code removal in CcBinary.
--
MOS_MIGRATED_REVID=99716999
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99716226
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99715964
|
|
|
|
|
|
|
| |
--
Change-Id: I46ad9d609af088e473ec478729a0b1c79cdf72f3
Reviewed-on: https://bazel-review.googlesource.com/#/c/1761
MOS_MIGRATED_REVID=99707451
|
|
|
|
|
|
|
| |
with Latin-1
--
MOS_MIGRATED_REVID=99651466
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
checking that are compatible with upcoming dynamic configurations (https://docs.google.com/document/d/1uoU8t7loTOu6uyzez-ilhcYgEXg4xjViJu0aqrf69TY/edit#heading=h.xsc8wmorka3u).
With today's configuration machinery, configuration equality means reference equality. With dynamic configurations, that won't necessarily be the case. This is primarily for two reasons:
1) Fragment-limited configurations means that a target's configuration only includes fragments needed by the target and its transitive closure. So if a java_library depends on a cc_library with the same configuration, the cc_library's instance won't contain the JavaConfiguration fragment.
2) The (upcoming) first pass of dynamic configurations uses old-style configurations for top-level targets, and dynamic configs for everything underneath. This can impact test calls that request a configured target both directly and as a dependency of another target. This distinction will eventually go away, but not yet.
Configurations that share the same options and fragments will continue to be reference-equal because of Skyframe caching.
--
MOS_MIGRATED_REVID=99610132
|
|
|
|
|
|
|
| |
[].
--
MOS_MIGRATED_REVID=99592972
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=99589366
|
|
|
|
|
|
|
|
| |
Don't log the actual message in interest of not spamming logs, for now. We can
use how common this is to determine if crashing is appropriate.
--
MOS_MIGRATED_REVID=99587448
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Query performance regression.
--
MOS_MIGRATED_REVID=99560234
|
|
|
|
|
|
|
|
|
|
|
|
| |
rules that can be removed.
What is left:
- The outputs of ExtractInclusionsAction. I think this action is shared between multiple rules that have the same generated file in srcs, so this call site is legitimate.
- Creating the solib symlinks. This is not a shared action, but these need to be in the same directory so that the RPATH is not too long, so we must live with this for the time being.
- FDO, which is beyond salvation. The artifacts under the FDO root don't really conform to the usual "only under the package directory" convention.
--
MOS_MIGRATED_REVID=99551394
|
|
|
|
|
|
|
|
|
| |
from previous builds with a different CPU do not end up in the APK.
Fixes #344.
--
MOS_MIGRATED_REVID=99550457
|
|
|
|
|
|
|
| |
bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change.
--
MOS_MIGRATED_REVID=99521906
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This introduces a new way to stop applications when deploying incremental
changes that saves the current app state for the next run. This allows things
like the back stack, and View/Fragment/Activity saved state to be restored when
the app next launches, making it easier to quickly iterate on code changes.
It adds a "--start" flag to mobile-install that replaces "--start_app".
--start accepts an argument describing the mode: no, cold, or warm. "no" is
now the equivalent of "--nostart_app", "cold" is the equivalent of
"--start_app", and "warm" is the new start mode.
Note that this is only useful with incremental installs, as Android clears out
any previously saved state when an APK is replaced.
--
MOS_MIGRATED_REVID=99508790
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99505283
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99500204
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99487015
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99486593
|
|
|
|
|
|
|
| |
It was previously allowed only in bzl files.
--
MOS_MIGRATED_REVID=99484302
|
|
|
|
|
|
|
|
|
| |
RuleContext#internalCreateOutputArtifact().
Fixes #351.
--
MOS_MIGRATED_REVID=99478770
|
|
|
|
|
|
|
| |
normal builds.
--
MOS_MIGRATED_REVID=99474480
|
|
|
|
|
|
|
| |
configuration can now be accessed via ctx.configuration.CONF where CONF is in {cpp, jvm, java}.
--
MOS_MIGRATED_REVID=99470271
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Various targets in nightly broken.
--
MOS_MIGRATED_REVID=99466859
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99453475
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99411524
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99411089
|
|
|
|
|
|
|
|
|
| |
This means Skyframe's change pruning can work more efficiently. Without the
overridden implementations we'd compare equal FEVs as inequal and unnecessarily
re-evaluate SkyKeys that we could have verified clean.
--
MOS_MIGRATED_REVID=99397188
|