CameraStreamBuffering test case intentionally calls
setMaxFramesInFight() with very large integer value to verify that API
handles unreasonaly large value properly. A type of its parameter is
changed from unsigned 32-bit integer to signed 32-bit integer in the
latest EVS interface definition written in the stable AIDL. To adapt a
test case, this CL updates it to use std::numeric_limits<int32_t>::max()
instead of 0xFFFFFFFF, which is translated as -1 in signed 32-bit integer
format.
Bug: 226628778
Test: atest VtsHalEvsV1_1TargetTest
atest VtsHalEvsTargetTest
Change-Id: Ic35c6c962617825bc271cec8544770340db7728a
Prior to this change, if IDevice::prepareModel* was passed a null
callback, the code would still attempt to call "notify" on the callback
to return the error to the client. This CL ensures the "notify" method
will not be invoked if the callback is null.
Bug: 230914930
Test: mma
Test: presubmit
Change-Id: I4a15d02c4879a0261ec26cc0e7a47d0a4da86b8b
Merged-In: I4a15d02c4879a0261ec26cc0e7a47d0a4da86b8b
(cherry picked from commit d6f6d01499)
Should use "ro.board.first_api_level" for vendor freeze project
Bug: 228778569
Test: run cts VtsHalMediaOmxV1_0TargetStoreTest pass
Change-Id: Ib46206be6267a44aaa0a8235a4f017569bb4de94
(cherry picked from commit a8c914ae69)
Merged-In: Ib46206be6267a44aaa0a8235a4f017569bb4de94
NNAPI NN_TRY macros use Statement Expressions (a GNU extension) to
propagate errors. However, a "return" statement in a Statement
Expression can lead to memory leaks when the Statement Expression is
being used to initialize a member of a struct. Specifically, when one member of a struct is already initialized, and a Statement Expression used to initialize a subsequent member early-returns, the previously initialized members will not have their destructors called.
This CL moves any NN_TRY macro out of struct initialization to avoid any
potential memory leaks.
Bug: 230500484
Test: mma
Test: presubmit
Change-Id: I3493fd4764f8eacc86750e6414e62bc891abaccd
The GNSS chipset must report measurements at the requested rate if
location is not requested.
Bug: 206670536
Test: doc update only
Change-Id: I3b488f8b38def4b6ebf13733149d9b75b23db0cb
The current matrix should not be used in Android T. However, it is left
here so that any late fixes to the T matrix can be made in a way that
will flow downstream.
Reason for 'DO NOT MERGE' - avoid landing this change in goog/master,
since the current matrix has HALs added there, some devices may be
relying on it.
In order to allow the (AOSP subset of) the T manifest to be frozen in
AOSP, and the current matrix to be enabled from aosp/master -..->
goog/master, this will be reverted in tm-dev-plus-aosp immediately after
it merges.
Bug: 203103997
Test: boot devices and vts_treble_vintf_vendor_test passes
Change-Id: I15bacedd0820e0086a742b97ee18e097ef8086e5
It was missing in the prior attempt to finzalize all AIDL interfaces.
Bug: 230660133
Test: m nothing
Change-Id: Icc319c84d57639ce083730a8bf15957e3ab7fe1d
Need to apply the sub-HAL index byte to ensure handles provided in
DYNAMIC_SENSOR_META events align properly with the [dis]connected
callbacks.
Bug: 228879057
Test: try on device with dynamic sensors sub-HAL at index > 0
Merged-In: Ic7290b51733bb829a5494ef41e9430b51dc6074e
Change-Id: Ic7290b51733bb829a5494ef41e9430b51dc6074e
For IBurst, a slot value of -1 indicates the slot should be ignored.
However, GeneratedTestHarness still attempts to call
IBurst::releaseMemoryResource on ignored slots. Instead, we should skip
releasing any ignored slots.
Bug: 230103381
Test: mma
Test: VtsHalNeuralnetworksTargetTest
Test: presubmit
Change-Id: I82e538aa0fd9e8ecc077df1c1ceece46a6166e67
Use the frozen kernel configs, not the 'current'
unfrozen kernel configs.
Test: TH
Fixes: 230144764
Change-Id: I2c6b1a1d5ec81acfb60380efeca0e6ee24b33089
Before checking the service specific error
we need to check that getExceptionCode returns
EX_SERVICE_SPECIFIC error code. Added a method and
used that to do the two checks together for exceptionCode
and for the service specific error code, so that we don't
repeat two lines in all the tests that need them.
EXPECT_NO_FATAL_FAILURES print the correct line number of the test
or iteration of the test when used with helper functions, and
testing guidelines recommend it too here: go/gunitadvanced#propagating-fatal-failures
Test: atest VtsHalGraphicsComposer3_TargetTest
BUG: 205152739
Change-Id: I1d3c3aa9b34dcefb14be507ff61b73b6f08a5204
The current matrix is left in this same CL because this way, downstream
modifications to the current CL will automatically get absorbed into the
level 8 compatibility matrix. A CL on top of this will disable the 7
matrix and then get reverted in the aosp/master..goog/master merge
path.
Bug: 203103997
Test: boot, vts_treble_vintf_vendor_test
Change-Id: I5c04d26e2b4dd0aac6e7d6ce3c72496081e9539d
TV devices can list a lot of configurations and have low
performing CPUs which causes the test to run for a significant
amount of time. From b/229824670 it seems that 10 minutes
should be enough.
Bug: 229824670
Test: atest VtsHalAudioV6_0TargetTest
Test: atest VtsHalAudioV7_0TargetTest
Test: atest VtsHalAudioV7_1TargetTest
Change-Id: Id7fa8eaa98bf2437fd1f676b9e5a7290df260fbd
(cherry picked from commit 0b9b03eb71)
Merged-In: Id7fa8eaa98bf2437fd1f676b9e5a7290df260fbd
VtsHalCanBusV1_0TargetTest needs buses brought up. On GSI images,
canhalctrl doesn't exist, so we have to attempt it on our own.
Bug: 213841914
Test: VtsHalCanBusV1_0TargetTest
Change-Id: I5553a95d047aef8e9d8e1eb6092cddea98f6d81e
