tree cf171962f34e5bcae5c39ab9883a54c244293322
parent aa422681a68e8ec7cdfce7e543295548a528f289
author Jeff Sharkey <jsharkey@android.com> 1509905858 -0700
committer Jeff Sharkey <jsharkey@android.com> 1509907476 -0700

Don't drop system server StrictMode violations.

The system server doesn't have a ProcessRecord, and all the
downstream already checks if it's null.  (Someone incorrectly added
a bailout-when-null check.)

We've actively burned down the number of system violations to a
minimum, and we're chasing the remaining violations with the intent
of them staying at 0, meaning we're okay to remove the batching
logic.  (The output format of batched violations is tricky for
dashboards to parse.)

Test: cts-tradefed run commandAndExit cts-dev -m CtsOsTestCases -t android.os.cts.StrictModeTest
Bug: 68662870
Change-Id: Ic1b81200c9550a316939e890a8cea8f37cfbb30b