Stub out code and test directories
BUG: 290094832
Test: atest FrameworksNetTests RemoteAuthUnitTests
Change-Id: I850242640f32bea3d46febcde5f3719619b1ea07
Casey Bordersauthored and Salil Rajadhyakshacommited 2023-07-31 21:41:26 +00:00
aosp/2605757 changed onNetworkActive callback behavior on U+ but this
change was not merged to U release branch.
This CL reverts the behavior change and keep the current behavior on U+.
Bug: 279380356
Bug: 291870075
Test: atest FrameworksNetTests
Change-Id: I91ccc7ee93f0827986401f316997b4a2df11318f
This commit updates test to
- Execute IkeSessionCallback inside executor. The callback should
be called from executor in production code but test trigger the
callback from test main thread which will result in unexpected
code interaction.
- Verify the timer directly. The origin design verifies
interactions with Captor with uncertain interaction. Test
should be able to verify the schedule() calls with the expected
timeout value. Also, in lower performance device, device may
still process previous interaction. Add longer timeout to reduce
flakes.
Bug: 293233390
Test: atest FrameworksNetTests
Test: atest VpnTest#testStartPlatformVpnFailedWithRecoverableError
--rerun-until-failure 100
Change-Id: Ie42a2597a382800d6484a086b6d808490dfbdd32
* changes:
Unregister BroadcastReceiver and OnSubscriptionsChangedListener.
Disable KeepaliveStatsTracker before T.
Disable KeepaliveStatsTracker instead of throwing.
Hansen Kurliauthored and Gerrit Code Reviewcommited 2023-07-28 11:20:21 +00:00
The first tethering test case may experience tethering restart
with IP conflict handling. Tethering would cache the last
upstreams so that the next enabled tethering avoids
picking up the address that is in conflict with the upstreams.
To protect subsequent tests, turn tethering on and off before
running them.
Bug: 254183718
Test: atest CtsTetheringTest
atest MtsTetheringTestLatestSdk
Change-Id: I03729d3212a03bd9fcfe2c09cf327840f13b250c
Markauthored and Mark Chiencommited 2023-07-27 16:04:28 +00:00
In failed log, VPN still process the migration which does not
send the network capabilities update to network agent.
In low performance devices like cuttlefish, it may sometimes
cause flaky. Specify a longer timeout to deflake the test.
Bug: 293233390
Test: atest FrameworksNetTests
Change-Id: I4e6c80c03e19efb448ee2806c5a250425b0e068f
chiachangwangauthored and Chiachang Wangcommited 2023-07-27 09:17:00 +00:00
Listen SoftAp callback to make sure soft ap is disabled
before start hotspot.
Bug: 277856014
Test: atest ConnectivityManagerTest#testFactoryReset
Change-Id: I95050be703b7c97da7a14541ac74718fdcbd7f13
Skip presubmit for tests that have been reported to be >0.5% flaky in
presubmit, or in mainline-presubmit. Tests that only meet that criteria
in mainline-presubmit are only marked as @SkipMainlinePresubmit.
Ensure that the tests are still run in postsubmit so they can be moved
back to presubmit after getting fixed.
Test: TH
Bug: 284534251
Bug: 292174275
Bug: 292173706
Bug: 292174832
Bug: 289879947
Bug: 286701510
Bug: 293239598
Bug: 279846955
Bug: 277567450
Bug: 293239828
Bug: 293240365
Change-Id: I986a1079709057d3210016c50b632fe0f3bff1e2
Inital commit for RemoteAuth adding the directory and the
OWNERS.
BUG: 290094832
Test: atest FrameworksNetTests
Change-Id: I8f5f109b7b01238388152c5a1caee72a753fe7fd
This is trivial - as the UDPLITE pseudoheader is identical
to the UDP pseudoheader (except that the UDPLITE pseudo length
is derived from the IPv4 total length / IPv6 payload length
field, instead of being copied from the UDPLITE header 'coverage
length' field - but this doesn't matter, as it [ie. the udplite
payload length] doesn't change during 464xlat translation).
Additionally UDPLITE never sends a checksum value of 0,
as at least 8 bytes (the UDPLITE header) *must* be included
in the checksum field, and a 0 must be sent as 0xFFFF.
See: https://datatracker.ietf.org/doc/html/rfc3828
Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I00a110b793fcf3cf705a9a706811da7866c3e810
Maciej Żenczykowskicommited 2023-07-25 16:17:48 +00:00
This fixes the flakiness. Because we call to a real server,
the server may not be reachable and our assumption would fail.
When this happens, the stream hangs and engine shutdown fails with
active request error. Hence cancel the stream before calling
shutdown.
Also @Ignored this test despite the fix as a safety measure to meet
the SLO. Will re-enable afterwards.
Bug: b/292298108
Test: atest NetHttpCoverageTests --test-filter
BidirectionalStreamTest#testBidirectionalStream_GetStream_CompletesSuccessfully
Change-Id: Iaae61fc62a148b58af86fb29c248399041785f9b
Change-Id: Iea9ef0b8468ec6fa05c306ea394485cec706b9ef
While previous tests benchmarking performance of reading
NetworkStatsCollection, this measures performance impact
caused by implementation of FileRotator.
Test: atest ConnectivityBenchmarkTests
Bug: 269409485
Change-Id: Ifcfc034128d6d78d759f80a43785b9f2b1ebb9c9
Add a test for benchmarking NetworkStatsCollection.
The test use data that generated from real user dataset which
has many uid records and agreed to share the dataset for testing
purpose.
Test: atest ConnectivityBenchmarkTests
Bug: 269409485
Change-Id: I8981bfc9f65636897c6fc735cda5353b448a0db2
When ServiceTypeClient is not used, the Executor threads should be
shutdown as well.
Bug: 287013457
Test: atest CtsNetTestCases FrameworksNetTests
Change-Id: I9dae01e7b6c2bcd395a98f4362f0c36f1535b2a6
Collect information about registration successes, failures, and
unregistrations, then build metrics data from this information
and report it.
Bug: 287546772
Test: atest FrameworksNetTestCases NsdManagerTest
Change-Id: I6324279b479da2e61b7519d96df5ad24a432e54a
If the tethering interface disappears while in server mode (i.e.
tethering is enabled), registering a new InterfaceStateListener will
trigger an NPE.
Test: TH
Bug: 290971780
Change-Id: I1d10575e80e68c77ec4771ac37e5fbc07e03c708
Add helper class NetworkNsdReportedMetrics to build and report
nsd metrics data.
Bug: 287546772
Test: m
Change-Id: I8271811c52a88329fd54e8e0f6cc455d3a3d22f7
Tests verifies the behavior with v4 mapped v6. The
taken parameter should be a v6 address. However,
InetAddresses.parseNumericAddress() will translate a v4
mapped v6 address into v4. This does not actually test
the behavior. The constant should be created via
Inet6Address.getByAddress() so that it will be an
expected Inet6Address.
Bug: 291869581
Test: atest NattKeepalivePacketDataTest
w/ and w/o aosp/2626269
Change-Id: I2f086f0fe7d1dd038f5d850f2281deb807c837cf
Casey Borders
authored and
Salil Rajadhyaksha
commited 
Motomu Utsumi
authored and
Gerrit Code Review
commited 
Chiachang Wang
authored and
Hansen Kurli
authored and
Junyu Lai
authored and
Mark Chien
authored and
Treehugger Robot
authored and
Remi NGUYEN VAN
authored and
Chalard Jean
commited 
Mike Yu
authored and
Paul Hu
authored and
Chidera Olibie
commited 
Maciej Żenczykowski
commited 
Yuyang Huang
authored and
Patrick Rohr
commited