In most places the `@hide` doctag is treated as a block tag on its own
line. However, there are a few places where it is treated as an inline
doctag, e,g. `{@hide}`, and some places where it looks like a block
tag but is inline in the text, e.g. `Some text. @hide`. Dealing with
all the types increases the complexity of Metalava and makes it
slightly slower.
This change replaces the non-block tag forms with a block tag.
Flag: EXEMPT change the form of @hide does not change the API or behavior
Bug: 429965593
Test: m checkapi
Change-Id: I4ffe44a329dbcb7f0a7bd61af16c3bd99cacdac4
This reverts commit e7a349bec4.
Reason for revert: broke the build in b/435385483.
Low-Coverage-Reason: This change reverted the previous broken change and will not change testing coverage.
Change-Id: Ifcef4eca52f7a952127ad628627afa3d24248bf4
This removes Nearby unittest dependences on BLE hardware and get rid of
flaky tests periodically reported from release testing.
Bug: 430923101
Test: atest NearbyUnitTests
Flag: EXEMPT mainline
Change-Id: If5527a47efa7513c463b50ec5529c8c9eae74300
.toList() was only introduced to android in api level 34, which is newer than
this module's min_sdk_version. Replace it with .collect().
This was found while updating android lint.
Flag: EXEMPT refactor
Bug: 394096385
Test: Presubmits
Change-Id: I472bff7749aebb21bd8681ecf4235ce7a6cfc7de
This avoids allocating a size which is read in from another process, which can cause OOM conditions and a crash.
Bug: 370353559
Change-Id: Iff9d4c8f63ba44ae64414d5143bfbb69b9966132
Test: TH
Steven Morelandcommited 2024-12-18 17:19:10 -08:00
Android 16 introduces restrictions on the DeviceConfig flags that
can be modified by the shell user by removing the WRITE_DEVICE_CONFIG
permission from this user and replacing it with the
WRITE_ALLOWLISTED_DEVICE_CONFIG permission; with this permission,
only those flags that have been allowlisted can be modified. This
commit adds the ALLOWLISTED permission to any test that explicitly
adopts the shell permission identity with the WRITE_DEVICE_CONFIG
permission; the WRITE_DEVICE_CONFIG permission is not removed to
ensure tests do not break when run on previous platform releases
without the ALLOWLISTED permission.
Bug: 364083026
Flag: TEST_ONLY
Test: Manually ran all modified tests
Change-Id: Iad68063550f99f3dc78ac2f0483dad98a8a93f2e
Michael Groovercommited 2024-11-18 23:28:24 -06:00
The APIs were not deleted to support the CTS before R5 test. Now that CTS R5 (without calling the APIs) is rolled out, we can remove these APIs.
Test: -m
Fix: 286137024
Bug: 376002171
Change-Id: I0812792b445a30a9cd366b41515dd39b981ef5d3
modules should specify the submodule of java_sdk_library that the module
actually depends on
Test: CI
Bug: 358613520
Change-Id: I0367068c901df98483f6cf95160d3e7801881b0a
Connectivity repo now can use java_aconfig_library since this target is
available on all downstream branches.
Bug: 345121279
Test: TH
Change-Id: I6d267ddac89731a8efbef2ee98a3baa1df754ff5
The Lint FlaggedApi checks are currently configured as warnings. Add
existing violations to baselines files to prepare for turning the
FlaggedApi checks into errors.
Bug: 303434307
Test: treehugger
Flag: EXEMPT not possible to flag baseline changes
Merged-In: I990ce57cd5cdac44ee8b93565b45aa15790ad697
Change-Id: I990ce57cd5cdac44ee8b93565b45aa15790ad697
The BTAdapterUtils were known to be flaky.
We recently fixed it and updating the usage.
In this case it looks like it is preferable to use the Enable rule
Bug: 339585576
Test: atest CtsPermissionUiTestCases
Test: atest CtsBluetoothTestCases
Test: atest CtsNearbyFastPairTestCases
Flag: TEST_ONLY
Change-Id: Ic81c62ae8c99207880cc14ff3c7f83128bb9f75b
William Escandecommited 2024-05-14 00:43:15 +00:00
Interface only change, without actual use of the HAL API.
Bug: 307898240
Test: atest NearbyUnitTests
Change-Id: I00772535a8f9247794ff59e465ed2b5af19576b4
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
Change-Id: I243f17b3f0ad7af9ffa15ca242456e36688733f5
Merged-In: I243f17b3f0ad7af9ffa15ca242456e36688733f5
NewApi is a lint check that you don't call framework methods that were
introduced in versions later than your min_sdk_version. We want to
make this an error, so we're baselineing all existing issues.
This cl was generated automatically, by taking all the NewApi issues
from the reference baselines, and all the non-NewApi issues from the
existing checked in baselines.
Bug: 268261262
Test: Presubmits
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4ecdedda379e4e9040eb87b01dc3d8efb89be810)
Merged-In: I0393f24f101876abc458ca139eefdb279dcb2b03
Change-Id: I0393f24f101876abc458ca139eefdb279dcb2b03
Cole Faustauthored and Android Build Cherrypicker Workercommited 2024-01-25 02:41:58 +00:00
This commented out line references the old robolectric ("Robolectric_all-target") which is being replaced by Robolectric_all-target_upstream
Bug: 314757990
Test: none, this is simply removing a commented out dep.
Flag: NA
Change-Id: I25eed6cef457bada06289656745ca5b5286bb467
lintable modules currently pick up files named "lint-baseline.xml" to use as the
lint baseline implicitly. This is confusing because you could end up using the
baseline files in more modules than intended. Lint also has a feature where it
requests you remove unnecessary findings from the baseline file, so something
could be necessary for one module, but unnecessary for another that accidentally
picked up the baseline.
We're removing the implicit detection of the baseline file, which requires
all modules using it to list the baseline file explicitly.
Bug: 272769514
Test: Presubmits
Change-Id: If873a4ea20d73bb6268d83589c4fb3ebe54af664