New issue
Advanced search Search tips

Issue 661879 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Jan 15
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 800015



Sign in to add a comment

"org.chromium.android_webview.test.AwZoomTest#testMagnification" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Nov 3 2016 
"org.chromium.android_webview.test.AwZoomTest#testMagnification" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySQsSBUZsYWtlIj5vcmcuY2hyb21pdW0uYW5kcm9pZF93ZWJ2aWV3LnRlc3QuQXdab29tVGVzdCN0ZXN0TWFnbmlmaWNhdGlvbgw.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 by tapted@chromium.org, Nov 4 2016

Cc: boliu@chromium.org
Owner: mnaga...@chromium.org
Status: Available (was: Untriaged)
Times out. testMagnificationWithZoomSupportOff has @RetryOnFailure. I'll try adding that.

https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/172843
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/172711
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/172690
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_swarming_rel/builds/59515

org.chromium.android_webview.test.AwZoomTest#testMagnification (run #1):
junit.framework.AssertionFailedError: Criteria not met in allotted time.
	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:74)
	at org.chromium.android_webview.test.AwTestBase.pollInstrumentationThread(AwTestBase.java:523)
	at org.chromium.android_webview.test.AwZoomTest.waitForScaleToBecome(AwZoomTest.java:141)
	at org.chromium.android_webview.test.AwZoomTest.runMagnificationTest(AwZoomTest.java:180)
	at org.chromium.android_webview.test.AwZoomTest.testMagnification(AwZoomTest.java:193)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)


try run at 2016-11-02 19:16:01 UTC	(milo)	patchset	linux_android_rel_ng	(reported in 661879)
try run at 2016-11-02 16:32:32 UTC	(milo)	patchset	linux_android_rel_ng	(reported in 661879)
try run at 2016-11-02 15:48:45 UTC	(milo)	patchset	linux_android_rel_ng	(reported in 661879)
try run at 2016-11-01 16:50:04 UTC	(milo)	patchset	android_n5x_swarming_rel	
 
try run at 2016-10-29 00:40:57 UTC	(milo)	patchset	linux_android_rel_ng	
 
try run at 2016-09-27 01:34:00 UTC	(milo)	patchset	linux_android_rel_ng	
 
try run at 2016-09-23 21:48:11 UTC	(milo)	patchset	linux_android_rel_ng	
 
try run at 2016-01-27 15:01:20 UTC		patchset	linux_android_rel_ng	
try run at 2016-01-27 15:01:20 UTC		patchset	linux_android_rel_ng	
 
try run at 2015-04-11 03:26:06 UTC		patchset	linux_android_rel_ng	
try run at 2015-04-11 03:26:06 UTC		patchset	linux_android_rel_ng

Comment 2 by tapted@chromium.org, Nov 4 2016

Cc: -boliu@chromium.org mnaga...@chromium.org
Owner: boliu@chromium.org
ah. mnaganov comes up "inactive" in rietveld.
Project Member

Comment 3 by bugdroid1@chromium.org, Nov 4 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3ab9dabc6e54050b0dcadf010b917713eb3a9219

commit 3ab9dabc6e54050b0dcadf010b917713eb3a9219
Author: tapted <tapted@chromium.org>
Date: Fri Nov 04 05:09:03 2016

Mark flaky android AwZoomTest#testMagnification @RetryOnFailure.

BUG= 661879 
TBR=boliu@chromium.org

Review-Url: https://codereview.chromium.org/2474333002
Cr-Commit-Position: refs/heads/master@{#429788}

[modify] https://crrev.com/3ab9dabc6e54050b0dcadf010b917713eb3a9219/android_webview/javatests/src/org/chromium/android_webview/test/AwZoomTest.java

Comment 4 by tapted@chromium.org, Nov 4 2016

Labels: -Sheriff-Chromium
Status: Assigned (was: Available)

Comment 5 by boliu@chromium.org, Nov 4 2016

Cc: -mnaga...@chromium.org
Components: Mobile>WebView
Owner: ----
Status: Available (was: Assigned)

Comment 6 by ntfschr@chromium.org, May 8 2017

Labels: -Pri-1 OS-Android Pri-3
Adjusting priority as per new bug triaging guidelines

Comment 7 by jming@chromium.org, Jan 8 2018

Blocking: 800015
Project Member

Comment 8 by sheriffbot@chromium.org, Jan 10

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by ctzsm@chromium.org, Jan 15

Mergedinto: 800015
Status: Duplicate (was: Untriaged)
issue 800015 was actually assigned to me, both issues are tracking the same, I'll close this one in favor of the other.
►

Sign in to add a comment