Disable NativeAllocationRegisteryTest for native bridge
1. NativeAllocationRegistry API cannot be emulated properly when
executed in a natively bridged environment.
2. This is because the API assumes that a native callback address is
provided to the system in a jlong. Native bridge must wrap the callback,
which is of a guest CPU arch, with a host CPU arch runner (that the
system will actually be able to call). But jlong doesn't express function
prototype, so we don't know how to pass arguments and return the result.
3. At the same time, NativeAllocationRegistry APIs are internal only and
they are always compiled for native CPU architecture. Thus running test
under native bridge (with ABI translation) doesn't correspond to any real
life scenario. And so it is ok to exclude this case from CTS tests.
Test: cts-tradefed run cts -m CtsLibcoreTestCases \
-t libcore.libcore.util.NativeAllocationRegistryTest
(with and without native bridge)
Bug: 71386447
Bug: 72533441
Bug: 72740423
Change-Id: Iaf6d5d54cf7d5fc87223318382d3ca2b2fd588ad
Merged-Id: I9e77b65246df47c2e0adc2930ba7839a991a8985
(Cherry-picked from 3e4099c48010b76c871831d6eccec5b40629fabd)
2 files changed
