New issue
Advanced search Search tips

Issue 639453 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug


Show other hotlists

Hotlists containing this issue:
Payments-TechDebt


Sign in to add a comment

Strict Mode violation in testAddInvalidAddressAndCancel on L Consumer builds

Project Member Reported by donnd@chromium.org, Aug 19 2016

Issue description

The L Consumer build is reliably failing with a Strict Mode violation in PaymentRequestFreeShippingTest#testAddInvalidAddressAndCancel:

Failures: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=org.chromium.chrome.browser.payments.PaymentRequestFreeShippingTest%23testAddInvalidAddressAndCancel&testType=chrome_public_test_apk
Recent: https://build.chromium.org/p/chromium.android/builders/Lollipop%20Consumer%20Tester/builds/2136
Log output:
I 1499.367s run_tests_on_device(06157df65a06b231)  detected failure in org.chromium.chrome.browser.payments.PaymentRequestFreeShippingTest#testAddInvalidAddressAndCancel. raw output:
I 1499.367s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: numtests=1
I 1499.367s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: stream=
I 1499.367s run_tests_on_device(06157df65a06b231)    org.chromium.chrome.browser.payments.PaymentRequestFreeShippingTest:
I 1499.368s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: id=InstrumentationTestRunner
I 1499.368s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: test=testAddInvalidAddressAndCancel
I 1499.368s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: class=org.chromium.chrome.browser.payments.PaymentRequestFreeShippingTest
I 1499.368s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: current=1
I 1499.368s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS_CODE: 1
I 1499.368s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: test=testAddInvalidAddressAndCancel
I 1499.368s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: class=org.chromium.chrome.test.ChromeActivityTestCaseBase$ChromeUncaughtExceptionHandler
I 1499.369s run_tests_on_device(06157df65a06b231)    INSTRUMENTATION_STATUS: stack=android.os.StrictMode$StrictModeViolation: policy=2655 violation=2
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.os.StrictMode.executeDeathPenalty(StrictMode.java:1379)
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.os.StrictMode.access$1300(StrictMode.java:118)
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.os.StrictMode$AndroidBlockGuardPolicy.handleViolation(StrictMode.java:1372)
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.os.StrictMode$AndroidBlockGuardPolicy$1.run(StrictMode.java:1254)
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.os.Handler.handleCallback(Handler.java:739)
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.os.Handler.dispatchMessage(Handler.java:95)
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.os.Looper.loop(Looper.java:145)
I 1499.369s run_tests_on_device(06157df65a06b231)    	at android.app.ActivityThread.main(ActivityThread.java:6837)
I 1499.370s run_tests_on_device(06157df65a06b231)    	at java.lang.reflect.Method.invoke(Native Method)
I 1499.370s run_tests_on_device(06157df65a06b231)    	at java.lang.reflect.Method.invoke(Method.java:372)
I 1499.370s run_tests_on_device(06157df65a06b231)    	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)
I 1499.370s run_tests_on_device(06157df65a06b231)    	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)
I 1499.370s run_tests_on_device(06157df65a06b231)    
I 1499.370s run_tests_on_device(06157df65a06b231)    Search logcat for "StrictMode policy violation" for full stack.

 
Owner: rouslan@chromium.org
Do we have adb logcat for this failure?
Status: Assigned (was: Untriaged)
Components: -UI>Browser>Autofill>Payments UI>Browser>Payments

Sign in to add a comment