commit | 72df65b28de7cce69b1d606c4d2ebe588b83c69a | [log] [tgz] |
---|---|---|
author | Patrick Rohr <prohr@google.com> | Mon Jul 08 13:43:48 2024 -0700 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sat Jul 20 07:01:32 2024 +0000 |
tree | 5dabc553fa31c72fe06ccf24cb14b3e81b7d339e | |
parent | 71cfb04dfc2058f1040eb3f890efb6ee0efc18b4 [diff] |
Do not test Log.wtf reporting pipeline on V+ On U QPR3+, networking bpf programs are already loaded by netbpfload, so there is no point in checking the netbpfload result. The system will likely abort if anything was not loaded correctly. Checking the netbpfload result is only really relevant on devices before V that receive netbpfload via mainline update. In addition, removing the Log.wtf from V+ devices prevents Android Go devices that use non-updatable modules from reporting wtf logs for a very long time. Test: TH Bug: 351118770 (cherry picked from https://android-review.googlesource.com/q/commit:1c351b2c4aed13b6169cbb107f7a1488637dbdd5) Merged-In: I8a412cb25374f3637f2fbd89617baa58d41d8589 Change-Id: I8a412cb25374f3637f2fbd89617baa58d41d8589