Issue metadata
Sign in to add a comment
|
Build failure: org.chromium.chrome.browser.infobar.InfoBarTest is flakey |
||||||||||||||||||
Issue descriptionBuild is broken: browser_tests on Ubuntu-12.04 Revision range: chromium 403396 : 403397 Failing builders: Linux Tests (dbg)(1): https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20(dbg)(1)
,
Jul 1 2016
megjablon@ Could you please take a look. ea3202d691f6594fd34e9bbb699e866cd12a07a9 seems to related to this failure. https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/35112/steps/chrome_public_test_apk/logs/stdio https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/35110/steps/chrome_public_test_apk/logs/stdio I 483.894s run_tests_on_device(0cba90a3032fdbe3) detected failure in org.chromium.chrome.browser.infobar.InfoBarTest#testDataReductionPromoInfoBarDismissed. raw output: I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: numtests=1 I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: stream= I 483.894s run_tests_on_device(0cba90a3032fdbe3) org.chromium.chrome.browser.infobar.InfoBarTest: I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: id=InstrumentationTestRunner I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: test=testDataReductionPromoInfoBarDismissed I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: class=org.chromium.chrome.browser.infobar.InfoBarTest I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: current=1 I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS_CODE: 1 I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: test=testDataReductionPromoInfoBarDismissed I 483.894s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: class=org.chromium.chrome.test.ChromeActivityTestCaseBase$ChromeUncaughtExceptionHandler I 483.895s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS: stack=android.os.StrictMode$StrictModeViolation: policy=2655 violation=2 I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.os.StrictMode.executeDeathPenalty(StrictMode.java:1377) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.os.StrictMode.access$1300(StrictMode.java:116) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.os.StrictMode$AndroidBlockGuardPolicy.handleViolation(StrictMode.java:1370) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.os.StrictMode$AndroidBlockGuardPolicy$1.run(StrictMode.java:1252) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.os.Handler.handleCallback(Handler.java:733) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.os.Handler.dispatchMessage(Handler.java:95) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.os.Looper.loop(Looper.java:136) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at android.app.ActivityThread.main(ActivityThread.java:5001) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at java.lang.reflect.Method.invokeNative(Native Method) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at java.lang.reflect.Method.invoke(Method.java:515) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) I 483.895s run_tests_on_device(0cba90a3032fdbe3) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) I 483.896s run_tests_on_device(0cba90a3032fdbe3) at dalvik.system.NativeStart.main(Native Method) I 483.896s run_tests_on_device(0cba90a3032fdbe3) I 483.896s run_tests_on_device(0cba90a3032fdbe3) Search logcat for "StrictMode policy violation" for full stack. I 483.896s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_STATUS_CODE: -1 I 483.896s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_RESULT: shortMsg=android.os.StrictMode$StrictModeViolation I 483.896s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_RESULT: longMsg=android.os.StrictMode$StrictModeViolation: policy=2655 violation=2 I 483.896s run_tests_on_device(0cba90a3032fdbe3) INSTRUMENTATION_CODE: 0 I 484.983s run_tests_on_device(01ab756b0330210f) detected failure in org.chromium.chrome.browser.infobar.InfoBarTest#testDataReductionPromoInfoBarFreOptOut. raw output: I 484.983s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: numtests=1 I 484.983s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: stream= I 484.983s run_tests_on_device(01ab756b0330210f) org.chromium.chrome.browser.infobar.InfoBarTest: I 484.983s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: id=InstrumentationTestRunner I 484.984s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: test=testDataReductionPromoInfoBarFreOptOut I 484.984s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: class=org.chromium.chrome.browser.infobar.InfoBarTest I 484.984s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: current=1 I 484.984s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS_CODE: 1 I 484.984s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: test=testDataReductionPromoInfoBarFreOptOut I 484.984s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: class=org.chromium.chrome.test.ChromeActivityTestCaseBase$ChromeUncaughtExceptionHandler I 484.984s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS: stack=android.os.StrictMode$StrictModeViolation: policy=2655 violation=2 I 484.984s run_tests_on_device(01ab756b0330210f) at android.os.StrictMode.executeDeathPenalty(StrictMode.java:1377) I 484.984s run_tests_on_device(01ab756b0330210f) at android.os.StrictMode.access$1300(StrictMode.java:116) I 484.984s run_tests_on_device(01ab756b0330210f) at android.os.StrictMode$AndroidBlockGuardPolicy.handleViolation(StrictMode.java:1370) I 484.984s run_tests_on_device(01ab756b0330210f) at android.os.StrictMode$AndroidBlockGuardPolicy$1.run(StrictMode.java:1252) I 484.984s run_tests_on_device(01ab756b0330210f) at android.os.Handler.handleCallback(Handler.java:733) I 484.984s run_tests_on_device(01ab756b0330210f) at android.os.Handler.dispatchMessage(Handler.java:95) I 484.984s run_tests_on_device(01ab756b0330210f) at android.os.Looper.loop(Looper.java:136) I 484.984s run_tests_on_device(01ab756b0330210f) at android.app.ActivityThread.main(ActivityThread.java:5001) I 484.984s run_tests_on_device(01ab756b0330210f) at java.lang.reflect.Method.invokeNative(Native Method) I 484.985s run_tests_on_device(01ab756b0330210f) at java.lang.reflect.Method.invoke(Method.java:515) I 484.985s run_tests_on_device(01ab756b0330210f) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) I 484.985s run_tests_on_device(01ab756b0330210f) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) I 484.985s run_tests_on_device(01ab756b0330210f) at dalvik.system.NativeStart.main(Native Method) I 484.985s run_tests_on_device(01ab756b0330210f) I 484.985s run_tests_on_device(01ab756b0330210f) Search logcat for "StrictMode policy violation" for full stack. I 484.985s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_STATUS_CODE: -1 I 484.985s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_RESULT: shortMsg=android.os.StrictMode$StrictModeViolation I 484.985s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_RESULT: longMsg=android.os.StrictMode$StrictModeViolation: policy=2655 violation=2 I 484.985s run_tests_on_device(01ab756b0330210f) INSTRUMENTATION_CODE: 0
,
Jul 1 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b997073eee258ac2f56f291cec99bdef648f8cf4 commit b997073eee258ac2f56f291cec99bdef648f8cf4 Author: horo <horo@chromium.org> Date: Fri Jul 01 05:43:12 2016 Disable DataReductionPromo tests in InfoBarTest.java BUG=610757, 625038 TBR=megjablon Review-Url: https://codereview.chromium.org/2116743002 Cr-Commit-Position: refs/heads/master@{#403412} [modify] https://crrev.com/b997073eee258ac2f56f291cec99bdef648f8cf4/chrome/android/javatests/src/org/chromium/chrome/browser/infobar/InfoBarTest.java
,
Jul 7 2016
See https://bugs.chromium.org/p/chromium/issues/detail?id=608223. This type of violation is due to a disk mode read from using the calendar.
,
Jul 7 2016
,
Jul 8 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8fcd3f03a3a531f12bb291dc8665834d85511c23 commit 8fcd3f03a3a531f12bb291dc8665834d85511c23 Author: megjablon <megjablon@chromium.org> Date: Fri Jul 08 22:07:01 2016 Re-enable DataReductionPromoInfoBar tests and fix flakiness StrictMode violation was from Calendar.getInstance() reading the /etc/timezone file. Whitelist the StrictMode violation to be fixed. Tests were flaky because the UI thread would not always launch the InfoBar before calling addInfoBarAnimationFinished(). Run the UI thread blocking so that the InfoBar has always been launched. BUG= 625038 , 577185 Review-Url: https://codereview.chromium.org/2130083002 Cr-Commit-Position: refs/heads/master@{#404506} [modify] https://crrev.com/8fcd3f03a3a531f12bb291dc8665834d85511c23/chrome/android/java/src/org/chromium/chrome/browser/infobar/DataReductionPromoInfoBar.java [modify] https://crrev.com/8fcd3f03a3a531f12bb291dc8665834d85511c23/chrome/android/javatests/src/org/chromium/chrome/browser/infobar/InfoBarTest.java
,
Jul 11 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/497683de6aa37f9a912b5b62808c84d82f987b67 commit 497683de6aa37f9a912b5b62808c84d82f987b67 Author: picksi <picksi@chromium.org> Date: Mon Jul 11 10:48:15 2016 Revert of Re-enable DataReductionPromoInfoBar tests and fix flakiness (patchset #3 id:60001 of https://codereview.chromium.org/2130083002/ ) Reason for revert: A number of related tests have started failing (see https://bugs.chromium.org/p/chromium/issues/detail?id=627038) Original issue's description: > Re-enable DataReductionPromoInfoBar tests and fix flakiness > > StrictMode violation was from Calendar.getInstance() reading > the /etc/timezone file. Whitelist the StrictMode violation > to be fixed. > > Tests were flaky because the UI thread would not always launch > the InfoBar before calling addInfoBarAnimationFinished(). Run > the UI thread blocking so that the InfoBar has always been > launched. > > BUG= 625038 , 577185 > > Committed: https://crrev.com/8fcd3f03a3a531f12bb291dc8665834d85511c23 > Cr-Commit-Position: refs/heads/master@{#404506} TBR=dfalcantara@chromium.org,megjablon@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG= 625038 , 577185 Review-Url: https://codereview.chromium.org/2135193002 Cr-Commit-Position: refs/heads/master@{#404629} [modify] https://crrev.com/497683de6aa37f9a912b5b62808c84d82f987b67/chrome/android/java/src/org/chromium/chrome/browser/infobar/DataReductionPromoInfoBar.java [modify] https://crrev.com/497683de6aa37f9a912b5b62808c84d82f987b67/chrome/android/javatests/src/org/chromium/chrome/browser/infobar/InfoBarTest.java
,
Jul 14 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ca4f3ba8a3522dbaf066b18465cf4cc322cdfb24 commit ca4f3ba8a3522dbaf066b18465cf4cc322cdfb24 Author: megjablon <megjablon@chromium.org> Date: Thu Jul 14 19:39:41 2016 Re-enable DataReductionPromoInfoBar tests and fix flakiness StrictMode violation was from Calendar.getInstance() reading the /etc/timezone file. Whitelist the StrictMode violation to be fixed. Tests were flaky because the UI thread would not always launch the InfoBar before calling addInfoBarAnimationFinished(). Run the UI thread blocking so that the InfoBar has always been launched. BUG= 625038 , 577185, 627038 Committed: https://crrev.com/8fcd3f03a3a531f12bb291dc8665834d85511c23 Review-Url: https://codereview.chromium.org/2130083002 Cr-Original-Commit-Position: refs/heads/master@{#404506} Cr-Commit-Position: refs/heads/master@{#405545} [modify] https://crrev.com/ca4f3ba8a3522dbaf066b18465cf4cc322cdfb24/chrome/android/java/src/org/chromium/chrome/browser/infobar/DataReductionPromoInfoBar.java [modify] https://crrev.com/ca4f3ba8a3522dbaf066b18465cf4cc322cdfb24/chrome/android/javatests/src/org/chromium/chrome/browser/infobar/InfoBarTest.java
,
Jul 15 2016
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by horo@chromium.org
, Jul 1 2016Status: Assigned (was: Available)