New issue
Advanced search Search tips

Issue 835585 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 831818
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug

Blocking:
issue 831818



Sign in to add a comment

"MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM/0" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Apr 21 2018

Issue description

"MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM/0" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyVgsSBUZsYWtlIktNU0VfRXh0ZXJuYWxDbGVhcktleS9FbmNyeXB0ZWRNZWRpYVRlc3QuUGxheWJhY2tfTXVsdGlwbGVfVmlkZW9BdWRpb19XZWJNLzAM.

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

This flaky test/step was previously tracked in issue 820285.
 
Blocking: 831818
Labels: -Sheriff-Chromium
Cc: jrumm...@chromium.org
Components: Internals>Media>Encrypted
Labels: OS-Mac
Owner: xhw...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 4 by chromium...@appspot.gserviceaccount.com, May 3 2018

Labels: Sheriff-Chromium
Detected 3 new flakes for test/step "MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM/0". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyVgsSBUZsYWtlIktNU0VfRXh0ZXJuYWxDbGVhcktleS9FbmNyeXB0ZWRNZWRpYVRlc3QuUGxheWJhY2tfTXVsdGlwbGVfVmlkZW9BdWRpb19XZWJNLzAM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).
Landing a patch to disable this test
Project Member

Comment 6 by bugdroid1@chromium.org, May 3 2018

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

commit a6594bc815d7d1d12e59730de3afc8f1416e4b9d
Author: jonross <jonross@chromium.org>
Date: Thu May 03 15:03:49 2018

Disable MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM

Currently MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM
is flaking on Mac. So I'm disabling it until that can be resolved.

TBR=xhwang@chromium.org
TEST=MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM

Bug:  835585 
Change-Id: Ifb82978c391d99804667c87a3d43ea1539bf9110
Reviewed-on: https://chromium-review.googlesource.com/1042373
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555732}
[modify] https://crrev.com/a6594bc815d7d1d12e59730de3afc8f1416e4b9d/chrome/browser/media/encrypted_media_browsertest.cc

Labels: -Sheriff-Chromium
Cc: dpranke@chromium.org
Status: Started (was: Assigned)
It seems to me the test just times out. Note that this one is among the slowest tests we have where it plays a video twice. Is it possible that this mac bot is slightly slower than others so the test timeouts more often?

To fix the issue, does it make sense to bump the timeout limit for browser_tests on this mac bot?

[690/873] MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM/0 (17514 ms)

https://logs.chromium.org/v/?s=chromium%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8947534405424895520%2F%2B%2Fsteps%2Fbrowser_tests__with_patch_%2F0%2Fstdout


Cc: mar...@chromium.org
+maruel for question on timeouts.py:

I also tried src/testing/buildbot/timeouts.py but it failed. I guess I don't really know what I am doing.

./timeouts.py -f chromium.mac.json -s browser_tests -N 200

0/5  Elapsed: 0.4sException in thread 0:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "./timeouts.py", line 111, in _run
    o = f()
  File "./timeouts.py", line 161, in <lambda>
    return lambda: query(server, number, builder, step)
  File "./timeouts.py", line 127, in query
    out = subprocess.check_output(cmd, stderr=subprocess.PIPE)
  File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
CalledProcessError: Command '['/usr/bin/python', '../../tools/swarming_client/swarming.py', 'query', '-S', 'ch
romium-swarm.appspot.com', '--limit', '200', 'tasks/list?tags=buildername%3AMac10.10+Tests&tags=name%3Abrowser
_tests']' returned non-zero exit status 2

.../chromium/src/testing/buildbot ./timeouts.py -f chromium.mac.json -s browser_tests -N 200
5/5  Elapsed: 7.7s  ETA: 0s   
Mac10.10 Tests       / browser_tests avg:  549s   max:  801s   timeout: 1560s
Mac10.11 Tests       / browser_tests avg:  443s   max: 1676s   timeout: 3360s
Mac10.12 Tests       / browser_tests avg:  391s   max:  500s   timeout:  960s
Mac10.13 Tests       / browser_tests avg:  486s   max:  656s   timeout: 1320s
Mac10.13 Tests (dbg) / browser_tests avg:  880s   max: 1154s   timeout: 2280s


I suspect it is because you need to auth first. Try running:
python ../../tools/swarming_client/swarming.py query -S chromium-swarm.appspot.com  server/details

and if it fails, it'll state the command to run, i.e.
python ../../tools/swarming_client/auth.py login -S chromium-swarm.appspot.com

Mergedinto: 831818
Status: Duplicate (was: Started)

Sign in to add a comment