| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102134151
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102126786
|
|
|
|
|
|
|
|
|
|
|
| |
is still broken owing to a bug in the code of the sandbox (#413)
The alternative to hand-listing the dependencies of apkbuilder is to glob all the jars in tools/lib. It would be more robust, but would take a little more time in the loading phase and on the startup of apkbuilder. Let's see how far we get with this approach.
Quite an embarrassing omission, owing to the lack of integration tests, which was in turn caused by us not having a continuous build. Now that we have one, we can actually write an integration test.
--
MOS_MIGRATED_REVID=102123234
|
|
|
|
|
|
|
| |
RELNOTES: deprecate the xcode_options flag
--
MOS_MIGRATED_REVID=102089578
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102083489
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102079110
|
|
|
|
|
|
|
| |
preperation for BazelProtoLibrary.
--
MOS_MIGRATED_REVID=102070904
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102059868
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102058774
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102057837
|
|
|
|
|
|
|
| |
Currently, this can only happen if a Skylark rules declare use of such an INTEGER_LIST.
--
MOS_MIGRATED_REVID=102054727
|
|
|
|
|
|
|
| |
XCODE_VERSION_OVERRIDE to executors if specified
--
MOS_MIGRATED_REVID=102049561
|
|
|
|
|
|
|
| |
given
--
MOS_MIGRATED_REVID=102046602
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102046532
|
|
|
|
|
|
|
| |
unavailable sandboxing.
--
MOS_MIGRATED_REVID=102042098
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102022958
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102020499
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101984361
|
|
|
|
|
|
|
| |
which is in line with the order of similar fields in ObjcProvider used for Bazel build.
--
MOS_MIGRATED_REVID=101979394
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101976891
|
|
|
|
|
|
|
| |
files.
--
MOS_MIGRATED_REVID=101975830
|
|
|
|
|
|
|
|
|
|
|
| |
resources to the test runner instead of ResourceContainers. Update AndroidLibraryAarProvider to contain transitive closure of .aars. Provides an ~4x speed improvement in test startup time.
NEW: Switched to ordered maps in CompositeLibraryAndroidManifestLocator to prevent manifest ordering flakiness bug. Switched to ImmutableSetMultimap in CompositeLibraryAndroidManifestLocator to prevent IllegalArgumentExceptions from duplicate package aliases and added test.
RELNOTES: android_resources is no longer allowed as a dep for android_robolectric_test.
--
MOS_MIGRATED_REVID=101972311
|
|
|
|
|
|
|
|
|
|
| |
Finding start/end line/col for locations takes some cpu work. As locations
are quite common this cpu work adds up. Instead make it possible to only
serialize the bare minimum location (start and end offset), the rest can
be derived from the original file if necessary.
--
MOS_MIGRATED_REVID=101966365
|
|
|
|
|
|
|
| |
RELNOTES: Change default value of objc_per_proto_includes to false
--
MOS_MIGRATED_REVID=101965455
|
|
|
|
|
|
|
| |
execution context instead of printing it to System.err.
--
MOS_MIGRATED_REVID=101941516
|
|
|
|
|
|
|
|
| |
Move away global constants and global namespaces out of Environment
and into a new file Runtime.
--
MOS_MIGRATED_REVID=101940218
|
|
|
|
|
|
|
| |
test script.
--
MOS_MIGRATED_REVID=101937276
|
|
|
|
|
|
|
|
| |
Allow a call to a struct's field when it's a function.
Check whether a java method exists before issuing KwArg error.
--
MOS_MIGRATED_REVID=101937143
|
|
|
|
|
|
|
|
|
|
|
| |
All the code paths to the baseline coverage action now go through the
InstrumentedFilesCollector, which only passes the local sources for baseline
coverage, which are only those files matching the instrumentation spec, which
in turn are only files that are valid for offline coverage (in combination
with the withBaselineCoverage flag).
--
MOS_MIGRATED_REVID=101935566
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101932897
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101930967
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We no longer generate baseline coverage for all transitive source files in
every target; instead, we generate baseline coverage for the files in the
current target and collect all of them transitively. That means much smaller
but more baseline coverage files; the total content is smaller if you were
providing more than one target with overlapping transitive closures on the
command line.
In addition, we now collect baseline coverage for all targets in the transitive
closure of the top-level targets. Previously, if you only passed test targets,
you would not get any baseline coverage.
--
MOS_MIGRATED_REVID=101929897
|
|
|
|
|
|
|
|
|
|
| |
Inline everything into the collect() method (which is now documented) and
clearly mark local sources (for future changes). Previously, we were creating
an intermediate object, which did all its work in the constructor. This means
less garbage and slightly clearer code flow (IMO).
--
MOS_MIGRATED_REVID=101927041
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101926862
|
|
|
|
|
|
|
|
|
|
| |
The baseline artifacts are part of the instrumented files provider now, and
are strongly tied to the collect_code_coverage flag. It seems to be simpler
to collect them explicitly in the BuildView (which already collects them for
post-processing), than to rely on the output group selection.
--
MOS_MIGRATED_REVID=101926341
|
|
|
|
|
|
|
| |
with --keep_going.
--
MOS_MIGRATED_REVID=101921704
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're currently doing too much work for baseline coverage - every rule creates
an action for its entire transitive closure; these actions are added to the
output group for baseline coverage, but not transitively accumulated.
It would be better for every rule to create an action for local baseline
coverage, and to aggregate the baseline coverage artifacts down the dependency
tree.
By merging the code paths, the InstrumentedFilesCollector can perform the
aggregation, because it can distinguish local and transitive files; I'm
planning to implement that in a subsequent change.
--
MOS_MIGRATED_REVID=101914334
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101913201
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101812326
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101809192
|
|
|
|
|
|
|
| |
This simplifies the users a bit, and makes it easier to refactor the code.
--
MOS_MIGRATED_REVID=101802767
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101798931
|
|
|
|
|
|
|
|
| |
This is necessary to have TargetResolver depend on it without making it depend
on the packages target. First step of #389.
--
MOS_MIGRATED_REVID=101790345
|
|
|
|
|
|
|
|
|
| |
rather than use a synchronized TreeSet that maintains the result in sorted order.
Consider M adds to the set resulting in N unique elements (so M >= N). The old approach was O(MlogN) and the new approach is O(M + NlogN) and has less lock contention; the time spent holding the lock is O(N) vs O(MlogN) - and actually ought to be small in practice because of the internal striping in CHS.
--
MOS_MIGRATED_REVID=101784791
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101777944
|
|
|
|
|
|
|
|
|
| |
Jack dexing currently only includes proguard specs from the binary itself,
not from any dependencies. There's no reason for this, just an accidental
inconsistency in the original implementation.
--
MOS_MIGRATED_REVID=101776897
|
|
|
|
|
|
|
| |
Symlink resolution did not work in all cases and broke ./compile.sh on certain Linux distros.
--
MOS_MIGRATED_REVID=101775459
|
|
|
|
|
|
|
| |
attributes: generator_{function, name, location}
--
MOS_MIGRATED_REVID=101774632
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101771182
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101769963
|