android_packages_modules_Co.../tests
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Remi NGUYEN VAN 43730b3f0f Add connectivity diagnostics on test failure
When CtsNetTestCases tests fail, or when a tryTest statement fails,
collect connectivity diagnostics and output them as a test artifact.

tryTest must be followed by cleanup blocks, which often change the
configuration, so having diagnostics when the tryTest fails in addition
to after the test failure is useful.

The collected diagnostics will be available as individual test
artifacts. They should make it easier to investigate test failures, and
could be collected across test runs in an automated way.

Output files are currently limited at 20 per run, to avoid collecting
too much data in case everything is failing in the run.

Test: atest
Change-Id: Iaa48e519028dc61c03d387beeade7d41fca2ef48
2024-10-16 10:05:35 +09:00
..
benchmark [DON'T BLOCK] Test ownership migration rules 2024-01-31 14:10:00 +00:00
common Remove module tests from FrameworksNetTests 2024-10-16 09:56:17 +09:00
cts Add connectivity diagnostics on test failure 2024-10-16 10:05:35 +09:00
deflake [DON'T BLOCK] Test ownership migration rules 2024-01-31 14:10:00 +00:00
integration Make java_sdk_library dependencies explicit 2024-09-10 00:01:31 +00:00
native Fix dependencies on connectivity_native lib 2024-07-31 00:39:50 +00:00
smoketest [DON'T BLOCK] Test ownership migration rules 2024-01-31 14:10:00 +00:00
unit Remove module tests from FrameworksNetTests 2024-10-16 09:56:17 +09:00