| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
| |
AutoCodec still cannnot handle types with generic elements, e.g.
class Foo<T> {
private T member;
}
PiperOrigin-RevId: 187052487
|
|
|
|
| |
PiperOrigin-RevId: 187048921
|
|
|
|
| |
PiperOrigin-RevId: 187044297
|
|
|
|
| |
PiperOrigin-RevId: 187043046
|
|
|
|
|
|
| |
class in https://github.com/bazelbuild/bazel/commit/14e549cc6596f67ed22c1bac0819f0775e4fb806).
PiperOrigin-RevId: 187042482
|
|
|
|
| |
PiperOrigin-RevId: 187038647
|
|
|
|
|
|
| |
Most of the time there's only one, doesn't justify the iterator overhead.
PiperOrigin-RevId: 187031802
|
|
|
|
| |
PiperOrigin-RevId: 187030267
|
|
|
|
|
|
|
|
|
|
|
| |
This cl introduces a bazel option
(--experimental_fix_linkstamp_inputs_bug_73447914) to control which inputs get
added into C++ linkstamp compile action. When set to true (defaults to false),
all inputs of relevant C++ linking action get added as inputs to the linkstamp
compile action too.
RELNOTES: None.
PiperOrigin-RevId: 187030217
|
|
|
|
| |
PiperOrigin-RevId: 187029559
|
|
|
|
| |
PiperOrigin-RevId: 187029004
|
|
|
|
| |
PiperOrigin-RevId: 187028864
|
|
|
|
| |
PiperOrigin-RevId: 187028110
|
|
|
|
|
|
|
|
|
|
|
| |
- collapsed these into one section
- removed the term "implicit outputs"
- add explanation for what these are first, then how to control them
- update docs for DefaultInfo
- also update docs for test/executable args of rule()
RELNOTES: None
PiperOrigin-RevId: 187026641
|
|
|
|
|
|
|
| |
This is a change from behavior introduced in unknown commit, which was added to preserve determinism even though the ordering of dicts in Python is non-deterministic. Now that we don't call into Python anymore, this is not necessary.
RELNOTES: None (select branches are mutually exclusive, so this is a no-op)
PiperOrigin-RevId: 187022575
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187018017
|
|
|
|
|
|
|
| |
Unified "Files" and "Output files" sections. Renamed "declared files" to "predeclared files" to avoid confusion with "declare_file()"/"declare_directory()".
RELNOTES: None
PiperOrigin-RevId: 187017607
|
|
|
|
|
|
|
|
|
|
| |
Dynamic environment variables are going away.
This also fixes a crashing bug.
Fixes #3983
RELNOTES: None.
PiperOrigin-RevId: 187008011
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Stamped binaries now have a correct
build-data.properties file with regard to the
"Build time" field.
There's a mismatch in BuildInfo.BUILD_TIMESTAMP
semantics between Bazel and Google-internal Blaze:
Bazel assumes this amount is in milliseconds,
Blaze assumed seconds.
Since there are users depending on this field
already on both sides, it is too late to change
its semantics. So this commit only fixes the
bogus "Build time" field and leaves
BUILD_TIMESTAMP as milliseconds for Bazel and as
seconds for Blaze.
Fixes https://github.com/bazelbuild/bazel/issues/4469
Change-Id: I28282d660244af693ab16443ae1e42fb455f9dde
PiperOrigin-RevId: 187005016
|
|
|
|
|
|
|
|
| |
This is a change from behavior introduced in unknown commit, which was added to preserve determinism even though the ordering of dicts in Python is non-deterministic. Now that we don't call into Python anymore, this is not necessary.
RELNOTES[INC]: The order of dict-valued attributes is now the order in the BUILD file (or in the Skylark dict they were created from) and not lexicographically sorted.
PiperOrigin-RevId: 187003317
|
|
|
|
|
|
| |
logic so that we can transparently handle arrays. We no longer care about the type of an object in AutoCodecProcessor: Marshallers is in charge of getting the correct code generator for array types anyway, so it can handle bare primitives as well.
PiperOrigin-RevId: 186919695
|
|
|
|
|
|
|
|
| |
(Des|S)erializationContext factories.
This is consistent as ObjectCodecs will eventually create context objects if needed.
PiperOrigin-RevId: 186900662
|
|
|
|
|
|
|
| |
This isn't 100% safe, which requires 1:1 type correspondence, but can catch
some errors at compile time.
PiperOrigin-RevId: 186898025
|
|
|
|
| |
PiperOrigin-RevId: 186849562
|
|
|
|
| |
PiperOrigin-RevId: 186837642
|
|
|
|
|
|
|
|
| |
* Deletes a number of CODEC references, now superceded by registry functionality.
* Minimal SkyKeySerializer modifications for correctness, as certain codec changes require
codecs to be in available in the registry.
PiperOrigin-RevId: 186834520
|
|
|
|
|
|
|
| |
See https://blog.bazel.build/2018/01/19/config-parsing-order.html for context on this change.
RELNOTES: --config flags now expand in place by default.
PiperOrigin-RevId: 186831701
|
|
|
|
|
|
|
|
|
|
| |
RuleConfiguredTarget. RuleConfiguredTarget is harder, and will be handled in a follow-up.
Also remove duplicate field from InputFileConfiguredTarget and unused parameter in EnvironmentGroupConfiguredTarget constructor.
Largely punt on FilesetOutputConfiguredTarget for now, but will handle soon.
PiperOrigin-RevId: 186829768
|
|
|
|
|
|
| |
serialize offset table at the cost of some overhead reconstructing the table. Also fewer code changes, although there is a serialization-only method added as a hack.
PiperOrigin-RevId: 186808832
|
|
|
|
|
|
|
|
|
|
| |
Skyframe native Filesets which reference output files.
We were failing to override equality of Artifact to use the artifact owner. See the javadocs on ArtifactSkyKey for more discussion of this.
Before this change, the weak interning of keys done in LegacySkyKey and FilesetEntryKey spuriously matched keys across incremental builds in cases where Artifacts differed only in their owner.
PiperOrigin-RevId: 186805663
|
|
|
|
|
|
|
|
|
|
| |
email from philwo@.
(i) Only have TimestampGranularityMonitor log the first file of relevance. This reduces log spam, especially in tests, while still maintaining useful information in the logs.
(ii) Don't have ExternalFilesHelper log the fact that it encountered an external file when we're in a unit test or an integration test. Tests, especially bazel tests that use external repositories, tend to involve lots of "external" files.
RELNOTES: None
PiperOrigin-RevId: 186799176
|
|
|
|
|
|
|
| |
AbstractAction had getPrimaryInput() and getPrimaryOutput()
which is why arguments are renamed.
PiperOrigin-RevId: 186795064
|
|
|
|
| |
PiperOrigin-RevId: 186789569
|
|
|
|
| |
PiperOrigin-RevId: 186789093
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
compilation with @androidndk//:toolchain-libcpp with missing link time files.
This fix needs a way to compare revision numbers, so the type of NdkRelease.majorRevision has been changed to Integer. This also paves the way for r15+ support.
Fixes https://github.com/bazelbuild/bazel/issues/3641
Fixes https://github.com/bazelbuild/bazel/issues/3923
Fixes https://github.com/bazelbuild/bazel/issues/4677
TESTED=bazel test //src/test/shell/bazel/android:android_ndk_integration_test with r11, r12, r13, r14, r15
RELNOTES: Fixed include paths for NDK r13+ llvm-libc++ headers to `ndk/sources/cxx-stl/llvm-libc++/include` and `ndk/sources/cxx-stl/llvm-libc++abi/include`
PiperOrigin-RevId: 186783465
|
|
|
|
|
|
| |
Fixes 4480.
RELNOTES: None.
PiperOrigin-RevId: 186774229
|
|
|
|
| |
PiperOrigin-RevId: 186772981
|
|
|
|
|
|
|
| |
Bazel because the test services APK is no longer installed by default as of unknown commit
RELNOTES: None.
PiperOrigin-RevId: 186772375
|
|
|
|
|
|
| |
different option values between two BuildOptions
PiperOrigin-RevId: 186769975
|
|
|
|
|
| |
Change-Id: Idb0c9fe770cd73c2760bee92997063c4c9b2e94e
PiperOrigin-RevId: 186768436
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fixed bug due to TransitiveTargetFunction requesting multiple Package dependencies when computing its aspect deps by only applying the optimization to TransitiveTraversalFunction.
*** Original change description ***
Automated rollback of commit cce164aed44aba1de244f0d764cd33a5cc6980b2.
PiperOrigin-RevId: 186766812
|
|
|
|
| |
PiperOrigin-RevId: 186765754
|
|
|
|
|
|
| |
SolibSymlinkAction.
PiperOrigin-RevId: 186765454
|
|
|
|
| |
PiperOrigin-RevId: 186765388
|
|
|
|
|
|
|
|
| |
Move dealing with coverage related features from CppConfiguration.configurationEnabledFeatures to CcCommon.configureFeatures.
Remove configurationEnabledFeatures.
RELNOTES: None.
PiperOrigin-RevId: 186744803
|
|
|
|
|
|
|
| |
constructor
RELNOTES: None.
PiperOrigin-RevId: 186744674
|
|
|
|
|
|
|
| |
android_local_test should not allow specifying resources and assets on the rule itself. If a user wants to add test specific resources/assets then they should wrap them in an android_library and add it to the deps of the android_local_test.
RELNOTES: None
PiperOrigin-RevId: 186724709
|
|
|
|
|
|
| |
This was already fixed in the file set, but was missed in important_output field.
PiperOrigin-RevId: 186711917
|
|
|
|
|
|
|
|
|
| |
consume binary resources.
This functionality is guarded by a flag, --experimental_android_local_test_binary_resources whose default value is false. If the flag is set to true, Bazel will generate the .ap_ and add the path to the .ap_ to the test_config.properties file. Bazel will still generate and pass the raw resources to Robolectric in both cases and so the cue to Robolectric that binary resources should be used is the presence of the path to the .ap_ in the test_config.properties file.
RELNOTES: None
PiperOrigin-RevId: 186708941
|
|
|
|
|
|
|
| |
android_local_test.
RELNOTES: None
PiperOrigin-RevId: 186699885
|