StrictMode policy violation in PaymentRequestPhoneAndFreeShippingTest_testPaymentRequestEventsMetric/0 |
|||||||
Issue descriptionbb748d47-c38d-4dcf-89cb-343cb554db83 Builders failed on: - Android Tests (dbg): https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29 I've seen several different payment related tests being flaky due to StrictMode violations on Android Tests (dbg) One or more of the following tests: PaymentRequestPhoneAndFreeShippingTest#testPaymentRequestEventsMetric PaymentRequestServiceWorkerPaymentAppTest#testHasSupportedPaymentMethods PaymentRequestEmptyUpdateTest#testSelectValidAddress PaymentRequestMultipleContactDetailsTest#testContactDetailsDedupe_Capitalization PaymentRequestEmailAndFreeShippingTest#testPay failed in these builds: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45586 https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45587 https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45554 Please take a look
,
Sep 15 2017
Another data point: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45611 Stack trace: android.os.StrictMode$StrictModeViolation: policy=2655 violation=2 at android.os.StrictMode.executeDeathPenalty(StrictMode.java:1377) at android.os.StrictMode.access$1300(StrictMode.java:116) at android.os.StrictMode$AndroidBlockGuardPolicy.handleViolation(StrictMode.java:1370) at android.os.StrictMode$AndroidBlockGuardPolicy$1.run(StrictMode.java:1252) at android.os.Handler.handleCallback(Handler.java:733) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:136) at android.app.ActivityThread.main(ActivityThread.java:5001) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) at dalvik.system.NativeStart.main(Native Method) Search logcat for "StrictMode policy violation" for full stack. Searching for native crashes in: /b/swarming/w/ite3KvMT/tmpgN9mSy Unknown Android release, consider passing --packed-lib. Reading Android symbols from: /b/swarming/w/ir Searching for Chrome symbols from within: /b/swarming/w/ir/out/Debug/lib.unstripped:/b/swarming/w/ir/out/Debug/lib:/b/swarming/w/ir/out/Debug Not sure how to best disable all of these tests, so leaving them enabled for now, but PTAL ASAP.
,
Sep 18 2017
To get the full stack as the error stack trace recommends, do the following: - Go to https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45611 - (Optional) Check non-green only - Open the result_details link in the failing target - Open link to failing test suite, in this case "org.chromium.chrome.browser.payments.PaymentRequestDynamicShippingSingleAddressTest" - Open logcat link besides failing test: testSelectValidAddressAndPay - Scroll up to find actual StrictMode stack trace 09-15 08:28:02.499 13536 13536 D StrictMode: StrictMode policy violation; ~duration=596 ms: android.os.StrictMode$StrictModeDiskReadViolation: policy=2911 violation=2 09-15 08:28:02.499 13536 13536 D StrictMode: at android.os.StrictMode$AndroidBlockGuardPolicy.onReadFromDisk(StrictMode.java:1135) 09-15 08:28:02.499 13536 13536 D StrictMode: at libcore.io.BlockGuardOs.open(BlockGuardOs.java:106) 09-15 08:28:02.499 13536 13536 D StrictMode: at libcore.io.IoBridge.open(IoBridge.java:393) 09-15 08:28:02.499 13536 13536 D StrictMode: at java.io.FileOutputStream.<init>(FileOutputStream.java:88) 09-15 08:28:02.499 13536 13536 D StrictMode: at java.io.FileOutputStream.<init>(FileOutputStream.java:73) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.DropBoxManagerService.add(DropBoxManagerService.java:211) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.os.DropBoxManager.addText(DropBoxManager.java:272) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActivityManagerService$17.run(ActivityManagerService.java:10018) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:10025) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActivityManagerService.handleApplicationWtf(ActivityManagerService.java:9832) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:337) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.util.Log$1.onTerribleFailure(Log.java:104) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.util.Log.wtf(Log.java:293) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.util.Slog.wtf(Slog.java:82) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActiveServices.killServicesLocked(ActiveServices.java:2081) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActivityManagerService.cleanUpApplicationRecordLocked(ActivityManagerService.java:12427) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActivityManagerService.handleAppDiedLocked(ActivityManagerService.java:3606) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActivityManagerService.appDiedLocked(ActivityManagerService.java:3751) 09-15 08:28:02.499 13536 13536 D StrictMode: at com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied(ActivityManagerService.java:1026) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.os.BinderProxy.sendDeathNotice(Binder.java:493) 09-15 08:28:02.499 13536 13536 D StrictMode: at dalvik.system.NativeStart.run(Native Method) 09-15 08:28:02.499 13536 13536 D StrictMode: # via Binder call with stack: 09-15 08:28:02.499 13536 13536 D StrictMode: android.os.StrictMode$LogStackTrace 09-15 08:28:02.499 13536 13536 D StrictMode: at android.os.StrictMode.readAndHandleBinderCallViolations(StrictMode.java:1705) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.os.Parcel.readExceptionCode(Parcel.java:1447) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.os.Parcel.readException(Parcel.java:1416) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.hardware.display.IDisplayManager$Stub$Proxy.getDisplayInfo(IDisplayManager.java:222) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.hardware.display.DisplayManagerGlobal.getDisplayInfo(DisplayManagerGlobal.java:117) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.view.Display.updateDisplayInfoLocked(Display.java:657) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.view.Display.getRotation(Display.java:533) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.display.PhysicalDisplayAndroid.updateFromDisplay(PhysicalDisplayAndroid.java:124) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.display.DisplayAndroidManager.addDisplay(DisplayAndroidManager.java:288) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.display.DisplayAndroidManager.initialize(DisplayAndroidManager.java:252) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.display.DisplayAndroidManager.getInstance(DisplayAndroidManager.java:202) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.display.DisplayAndroid.getManager(DisplayAndroid.java:57) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.display.DisplayAndroid.getNonMultiDisplay(DisplayAndroid.java:77) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.base.WindowAndroid.<init>(WindowAndroid.java:199) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.base.ActivityWindowAndroid.<init>(ActivityWindowAndroid.java:69) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.ui.base.ActivityWindowAndroid.<init>(ActivityWindowAndroid.java:60) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.chrome.browser.ChromeWindow.<init>(ChromeWindow.java:24) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.chrome.browser.ChromeActivity.createWindowAndroid(ChromeActivity.java:306) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.chrome.browser.init.AsyncInitializationActivity.onCreateInternal(AsyncInitializationActivity.java:278) 09-15 08:28:02.499 13536 13536 D StrictMode: at org.chromium.chrome.browser.init.AsyncInitializationActivity.onCreate(AsyncInitializationActivity.java:243) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.app.Activity.performCreate(Activity.java:5231) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.support.test.runner.MonitoringInstrumentation.callActivityOnCreate(MonitoringInstrumentation.java:532) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2148) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2233) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.app.ActivityThread.access$800(ActivityThread.java:135) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196) 09-15 08:28:02.499 13536 13536 D StrictMode: at android.os.Handler.dispatchMessage(Handler.java:1
,
Sep 20 2017
cc'ing another OWNER to speed up the process. payment's tests did fail in other builds as well https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45602 org.chromium.chrome.browser.payments.PaymentRequestJourneyLoggerTest#testUserHadCompleteSuggestions_AcceptsCardsAndApps_UserHasOnlyCard https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45619 org.chromium.chrome.browser.payments.PaymentRequestContactDetailsTest#testQuickCloseAndAddContactShouldNotCrash https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45665 org.chromium.chrome.browser.payments.PaymentRequestCanMakePaymentQueryTest#testPayViaSlowBobPay https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/45677 org.chromium.chrome.browser.payments.PaymentRequestDontHaveDebitTest#testCanMakePaymentWithUnknownCardType
,
Sep 22 2017
Mathieu could you please take a look? This is causing significant flakiness on the Chromium waterfall on the "Android Tests (dbg)" bot. Are these payment tests the cause of the StrictMode violation a more fundamental issue?
,
Sep 22 2017
,
Sep 22 2017
Elly: Can you provide us with the "adb logcat" of the failed test run? That's the only place that contains the stack trace that caused the strict mode violation, but I can't find it in the links that you've provided.
,
Sep 22 2017
Found the logcat here: https://luci-logdog.appspot.com/v/?s=chromium%2Fandroid%2Fswarming%2Flogcats%2F389d7181692ff011%2F%2B%2Flogcat_org.chromium.chrome.browser.payments.PaymentRequestDynamicShippingSingleAddressTest.testSelectValidAddressAndPay_20170915T082759-UTC_0cbbdb8c0c36f2d4 But it does not contain any payment package symbols...
,
Sep 22 2017
+cc ccameron Looks like violation happens in Android call android.view.Display.getRotation(Display.java:533), which is called from Chromium code org.chromium.ui.display.PhysicalDisplayAndroid.updateFromDisplay(PhysicalDisplayAndroid.java:124). Not sure we can do anything with Android system calls, except suppressing strict mode checks for that particular line of code.
,
Sep 25 2017
,
Sep 25 2017
This came up as well in issue 765936 .
,
Oct 23 2017
It looks like this is still happening: https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/412240 https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/412258 Maybe you could suppress the strict mode violation if there is no other way to fix this? This is done for loading preferences as well (https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/preferences/PreferenceUtils.java)
,
Oct 25 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dullweber@chromium.org
, Sep 14 2017