The parameters `actual` and `expected` in the macros EXPECT_{GE,GT,EQ}
can be a statement. If their returned value are different, it results
in them being called twice. Some statements are not supposed to be
called more than once, such as expectAnswersValid that automatically
closes the fd.
Bug: 242681575
Test: atest CtsNetTestCasesLatestSdk:MultinetworkApiTest
Change-Id: Id730bcc3248ae77fcf05db414a7f5a2fe1d212e3
Upcoming CL will update BpfNetMaps to pull NetworkBpfMapInfo atom that
contains the cookieTagMap size field.
Test: m, atest BpfNetMaps
Bug: 217624062
Change-Id: I84bb0aa56e3916fc6fc0ca31ba5962f3b9be4b6f
Give slack time for waiting UDP stream mode because handling conntrack
event in user space may not in precise time. Used to reduce the flaky
rate.
Bug: 243314243
Test: atest EthernetTetheringTest
Change-Id: I7aee1a45d9a4d4fecf09739488dcaadeb7e86655
This change moves ConnectivityChecker from `required` to `data`,
since the `required` is inherited from Make and is very vague. It's
discouraged by Android Build team to use it.
Besides, this change declares net-tests-utils-host-common, since Net
tests use ConnectivityCheckTargetPreparer that is included in
net-tests-utils-host-common. All dependencies of a test should be
declared explicitly, so that test infrastructure could only provide
the needed dependencies instead of all to run a test.
Bug: 222438068
Test: presubmit
Change-Id: Id522fd88ca53b5af338315fc6370d68bdabf403b
Switch existing C SkDestroyListener and new Java SkDestroyListener based
on the experiment flag.
Bug: 217624062
Test: atest SkDestroyListenerTest
Change-Id: I7031ba7c155edb43e0e7b77449587058d6ba38fb
This CL prepares for upcoming CL.
Upcoming CL will add SkDestroyListener with Java BpfMap and switch
current C SkDestroyListener and new Java SkDestroyListener based on the
experiment flag.
Bug: 217624062
Test: atest SkDestroyListenerTest
Change-Id: I5ebb319d1b2262199d4ef6a3549894fee24c4ccf
SkDestroyListener monitors the destroy of IPv4/IPv6 TCP/UDP sockets and
removes CookieTagMap entries.
SkDestroyListenerTest closes 100 sockets at once and check all the
entries are removed from the CookieTagMap.
Bug: 217624062
Test: atest MtsTetheringTestLatestSdk
Change-Id: I161006f4ae5bd83085e68bf8de260f04f3da0ea0
This will address flakiness issues arising from the use of
when() in multithread context.
Fix: 243658074
Test: atest com.android.server.net.NetworkStatsServiceTest#testDataMigration_differentFromFallback \
--rerun-until-failure 1000
Change-Id: I047050ef14cb60658098ff7803c6773907a92919
Require at least kernel 5.15. Feature is not required on older
kernels and may impact boot time unnecessarily.
Bug: 235559605
BUg: 241077401
Fixes: 241077401
Test: run cts -m CtsNetTestCases -t android.net.cts.DscpPolicyTest
Change-Id: I2e4b509de1d8940fc63ae057a8326f13c0fd1420
Merged-In: I2e4b509de1d8940fc63ae057a8326f13c0fd1420
since it doesn't actually work (this runs in netd, but is meant
to protect against system server modifications)
Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I87f268f1a68c559b19caa4d625cb9eb8395c91e2
These timestamps will be useful for debugging issues where
debuggers need to know what happened to long-lived networks,
where logcat doesn't span long enough.
These timestamps are also likely to be useful in the future,
in particular for metrics.
Test: FrameworksNetTests
Change-Id: I8f46ce92e2ab301fa32e18e714a43a4130719199
CtsNetTestUtils#connectToCell is happy to give an existing
cell network, so it doesn't make a lot of sense that it
demands only be called once per test unless you disconnect.
Some tests may face instability in the network and may
need to retry, but having the test itself know that
particular nook of the CtsNetTestUtils API is not very
seamless.
Instead, it's more useful to just unregister the callback
if it has been registered.
Test: CtsNetTestCases
Change-Id: I4dad570dcd2c25fb7ccd176769a805620fd8df59
aosp/2193727 adds BpfDump#dumpMap.
This CL updates NetworkStatsService to use this helper function.
Test: dumpsys netstats, atest NetworkStatsServiceTest
Change-Id: Ieaa75b6317678ef4f41d22c294e290c3a6d58fad
This might eliminate a failure mode with dreaded 524 error
from the kernel... or it might not, but it shouldn't hurt.
Bug: 230418056
Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: If2479daf77f61c220214ff507582295bd303fd21
When an app is removed, the stats still be included in
the persist snapshot in NetworkStatsFactory which
causes settings show the data usage with the uid of the
removed app. Thus, remove the stats of the removed
package from the persist snapshot when NetworkStatsService
receives ACTION_UID_REMOVED intent.
Bug: 239899930
Bug: 209360825
Test: FrameworksNetTests:NetworkStatsServiceTest
FrameworksNetTests:NetworkStatsFactoryTest
Change-Id: I73cca367ac6bf0d2d29ef0a7d94500f1e6917dcb
Currently, data usage of all test networks are all attributed to
the same NetworkIdentity, which does not allow services to
distinguish upload & download traffic of different test networks.
Thus, this CL put specifier that comes along with
TestNetworkAgent into wifiNetworkKey field to build different
NetworkIdentity to attribute data usage to different for
individual networks. And allow querying test network usage with
wifiNetworkKeys.
Bug: 139774492
Test: atest FrameworksNetTests
atest android.net.cts.ConnectivityManagerTest
Change-Id: I1bb38fd20781eaf3105735440a04b27bef36fcae
This reverts commit c2bc2963c1.
Reason for revert: fixed flakiness. Re-enable EthernetManagerTest in presubmit.
Change-Id: I29f7d2b4f530b18aaaae3e327f3721f08aab060a
Unfortunately, there is no way to disable carrier on the tap interface
without first configuring the interface with carrier. This means that it
is possible the interface is brought up before carrier is disabled (it
is an unlikely flake but it does happen in automation). Reenabling RS
delay and DAD will make sure that provisioning does not succeed before
carrier is disabled.
Test: atest EthernetManagerTest --iterations 50
Change-Id: Ie2aa7529b48fa9aceff3dd3b432d87a6eb2f0298
