lucaslin 20f7c6e60d Separate 2 tests to verify canBeSatisfiedBy() ...

In Android R, NetworkSpecifier#satisfiedBy() has changed to
NetworkSpecifier#canBeSatisfiedBy(), but its subclass -
MatchAllNetworkSpecifier hasn't.
In Android S, both of MatchAllNetworkSpecifier and
NetworkSpecifier has changed satisfiedBy() to canBeSatisfiedBy().
So if running the latest CTS on R device, it will verify
NetworkSpecifier#canBeSatisfiedBy() instead of
MatchAllNetworkSpecifier#satisfiedBy() and get the unexpected
result.
The fix is to separate 2 tests to verify canBeSatisfiedBy(), one
is for Android R or older version and the other is for Android
S+.

Bug: 172401624
Test: Run MatchAllNetworkSpecifierTest on Android R and S.
Change-Id: I1391bae9a0fc0298beb8fe80b5f388b492244566

2020-11-12 12:48:16 +08:00

core

Merge "Add maxTargetSdk restriction to unused APIs."

2020-11-09 14:41:20 +00:00

services/core

Merge changes I67e5fa23,I223b207c

2020-11-10 05:28:33 +00:00

tests/net

Separate 2 tests to verify canBeSatisfiedBy()

2020-11-12 12:48:16 +08:00

Description

android_packages_modules_Connectivity

189 MiB

Languages

Java 81.4%

Kotlin 7.7%

AIDL 4.5%

C++ 4.5%

C 1.7%

Other 0.1%