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

Issue 680348 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 685835
Owner:
not on Chrome anymore
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

video_decode_accelerator_unittest flaky on tryserver.chromium.angle win_angle_x64_rel_ng

Project Member Reported by ynovikov@chromium.org, Jan 12 2017

Issue description

Started here:
https://build.chromium.org/p/tryserver.chromium.angle/builders/win_angle_x64_rel_ng/builds/3255
Subsequent retry of the same patchset succeeded:
https://build.chromium.org/p/tryserver.chromium.angle/builders/win_angle_x64_rel_ng/builds/3256

Also here:
https://build.chromium.org/p/tryserver.chromium.angle/builders/win_angle_x64_rel_ng/builds/3271
Subsequent successful retry of the same patchset:
https://build.chromium.org/p/tryserver.chromium.angle/builders/win_angle_x64_rel_ng/builds/3272

Failing test is DecodeVariations/VideoDecodeAcceleratorParamTest.TestSimpleDecode/2
For some reason it fails to reach the expected 50 FPS:

[ RUN      ] DecodeVariations/VideoDecodeAcceleratorParamTest.TestSimpleDecode/2
[2836:3332:0111/160233.307:7423884:INFO:gpu_video_decode_accelerator_factory.cc(181)] Initializing DXVA HW decoder for windows.
[2836:3584:0111/160240.651:7431232:INFO:video_decode_accelerator_unittest.cc(1478)] Decoder 0 fps: 34.2637
e:\b\c\b\win\src\media\gpu\video_decode_accelerator_unittest.cc(1483): error: Expected: (client->frames_per_second()) > (min_fps), actual: 34.2637 vs 50
[  FAILED  ] DecodeVariations/VideoDecodeAcceleratorParamTest.TestSimpleDecode/2, where GetParam() = (1, 15, 1, -1, 6, false, false) (7393 ms)

 

Comment 1 by kbr@chromium.org, Jan 12 2017

Owner: jbau...@chromium.org
Status: Assigned (was: Available)
Mergedinto: 685835
Status: Duplicate (was: Assigned)
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 15 2017

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

commit b3fdd063a1128b441a232215a5798416c3b63ef4
Author: jbauman <jbauman@chromium.org>
Date: Wed Feb 15 11:08:00 2017

Remove min fps requirements for VDA unittest on windows bots.

These bots can be intermittently slow, so requiring 50 fps isn't
possible. This patch specifies in the command-line argument
to the test that there's no minimum fps on the test file that's used.
The tests will still fail and time out if they take way too long.

BUG= 680348 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

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

[modify] https://crrev.com/b3fdd063a1128b441a232215a5798416c3b63ef4/content/test/gpu/generate_buildbot_json.py
[modify] https://crrev.com/b3fdd063a1128b441a232215a5798416c3b63ef4/testing/buildbot/chromium.gpu.fyi.json
[modify] https://crrev.com/b3fdd063a1128b441a232215a5798416c3b63ef4/testing/buildbot/chromium.gpu.json

Sign in to add a comment