Loading
MM tests should fail if they produce unexpected wtf logs
In eng-builds, some misconfiguration in a MotionValue would cause a crash. However, in tests (and in production), we want animations to proceed even with such errors. When a test ends, we should check loggedFailures, if they were expected. Test: atest MotionValueTest Bug: 420622452 Flag: com.android.systemui.scene_container Change-Id: I640c21fde03785bd33920bb8a13b3bb866191d25