New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 625584 link

Starred by 6 users
Status: Duplicate
Merged: issue 656231
Owner:
█ zqzh...@chromium.org
Android MediaRouter only (left Chro...
Closed: Nov 2016
Cc:
█ zqzh...@chromium.org
mlamouri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

"content_shell_test_apk (with patch)" is flaky for java MediaSessionTest

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jul 4 2016 
"content_shell_test_apk (with patch)" is flaky for java MediaSessionTest.

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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLgsSBUZsYWtlIiNjb250ZW50X3NoZWxsX3Rlc3RfYXBrICh3aXRoIHBhdGNoKQw.



This flaky test/step was previously tracked in  issue 598482 .

Comment 1 by phoglund@chromium.org, Jul 6 2016

Labels: -Sheriff-Chromium
Owner: mlamouri@chromium.org
Status: Assigned (was: Untriaged)
Disable going in: https://codereview.chromium.org/2125863002/. mlamouri, please help with an owner (found you from blame in the test file).

Comment 2 by phoglund@chromium.org, Jul 6 2016

Labels: -Pri-1 Pri-2
Project Member

Comment 3 by bugdroid1@chromium.org, Jul 6 2016 

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

commit 53adfa415fbf9bcb34a1e988b83da7d42a1b4cf9
Author: phoglund <phoglund@chromium.org>
Date: Wed Jul 06 13:26:01 2016

Disabling flaky MediaSessionTest.testMediaDuck.

BUG= 625584 
TBR=mlamouri@chromium.org

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

[modify] https://crrev.com/53adfa415fbf9bcb34a1e988b83da7d42a1b4cf9/content/public/android/javatests/src/org/chromium/content/browser/MediaSessionTest.java

Comment 4 by mlamouri@chromium.org, Jul 6 2016

Cc: mlamouri@chromium.org
Owner: zqzh...@chromium.org

Comment 5 by zqzh...@chromium.org, Jul 6 2016

Labels: OS-Android
The logcats says the video is not loaded in DOM. Maybe we should run the tests with spitzer on to reduce the flakyness?


I  146.842s run_tests_on_device(03a5d5a10ae58ac6)  detected failure in org.chromium.content.browser.MediaSessionTest#testMediaDuck. raw output:
I  146.842s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: numtests=1
I  146.843s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: stream=
I  146.843s run_tests_on_device(03a5d5a10ae58ac6)    org.chromium.content.browser.MediaSessionTest:
I  146.843s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: id=InstrumentationTestRunner
I  146.843s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: test=testMediaDuck
I  146.843s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: class=org.chromium.content.browser.MediaSessionTest
I  146.843s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: current=1
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS_CODE: 1
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: numtests=1
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    INSTRUMENTATION_STATUS: stream=
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    Failure in testMediaDuck:
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    junit.framework.AssertionFailedError: Failed to retrieve contents for long-video
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.content.browser.test.util.DOMUtils.getNodeField(DOMUtils.java:385)
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.content.browser.test.util.DOMUtils.isMediaPaused(DOMUtils.java:73)
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.content.browser.test.util.DOMUtils$1.isSatisfied(DOMUtils.java:110)
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:72)
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.content.browser.test.util.DOMUtils.waitForMediaPlay(DOMUtils.java:105)
I  146.844s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.content.browser.MediaSessionTest.testMediaDuck(MediaSessionTest.java:324)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at java.lang.reflect.Method.invokeNative(Native Method)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.content_shell_apk.ContentShellTestBase.runTest(ContentShellTestBase.java:233)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
I  146.845s run_tests_on_device(03a5d5a10ae58ac6)    	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

Comment 6 by mlamouri@chromium.org, Jul 7 2016 

Spitzer should be enabled by default now. What makes you think it doesn't run with Spitzer?

Comment 7 by zqzh...@chromium.org, Jul 7 2016 

I remember in one meeting I heard that Spitzer did not ship in some version (M51?). So I thought it was still disabled by default. My great memory :(

BTW, I've seen this kind of issue several times before, not very clear how could this happen if it's not a pipeline issue.

Comment 8 by zqzh...@chromium.org, Aug 10 2016

Labels: -Pri-2 Pri-3

Comment 10 by xlai@chromium.org, Sep 12 2016

Labels: -Pri-3 Pri-2

Comment 11 by zqzh...@chromium.org, Sep 12 2016

Labels: -Pri-2 Pri-3
These flaky tests are not related to MediaSessionTest. This entry is only for MediaSessionTests.
Filed a new one, please find relevant owners. Filed https://crbug.com/645987

Comment 12 by zqzh...@chromium.org, Sep 12 2016

Description: Show this description

Comment 13 by zqzh...@chromium.org, Sep 12 2016

Summary: "content_shell_test_apk (with patch)" is flaky for java MediaSessionTest (was: "content_shell_test_apk (with patch)" is flaky)
Project Member

Comment 14 by chromium...@appspot.gserviceaccount.com, Oct 14 2016 

Detected 3 new flakes for test/step "content_shell_test_apk (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLgsSBUZsYWtlIiNjb250ZW50X3NoZWxsX3Rlc3RfYXBrICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app.

Comment 15 by zqzh...@chromium.org, Oct 14 2016

Cc: zqzh...@chromium.org
 Issue 589176  has been merged into this issue.

Comment 16 by zqzh...@chromium.org, Nov 3 2016 

 Issue 639175  has been merged into this issue.

Comment 17 by zqzh...@chromium.org, Nov 3 2016

Mergedinto: 656231
Status: Duplicate (was: Assigned)
►

Sign in to add a comment