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

Issue 676041 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

MANUAL_TestAcquiringAndReacquiringWebcam fails on Win8 bot for 720p

Project Member Reported by chfremer@chromium.org, Dec 20 2016

Issue description

WebRtcWebcamBrowserTest.MANUAL_TestAcquiringAndReacquiringWebcam [1] was failing on a Win 8 bot [2] for resolution 720p, see crbug.com/676020.

As a mitigation, we have disabled resolutions of 720p and up for Windows 8.

We should investigate if the cause is a physical webcam/driver that does not support this resolution. If that is the case, we should replace the webcam and reactivate the disabled resolutions in the test.

[1] https://chromium.googlesource.com/chromium/src/+/b5f5e5f36dc8ca72cf962feb70e9c3c3e2573e47
[2] https://build.chromium.org/p/chromium.webrtc/builders/Win8%20Tester



 
What's the point of this bug compared to bug 676020?
I thought bug 676020 is meant for tracking that the bot failures get mitigated.

So I created this new one for tracking the investigation into the webcam.
Fair enough. I guess we can merge the two depending on what the labs team can find.

Project Member

Comment 4 by bugdroid1@chromium.org, Dec 20 2016

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

commit f824c13d23fd8e7d91887f40d028d112765b73fe
Author: chfremer <chfremer@chromium.org>
Date: Tue Dec 20 23:39:51 2016

Disable failing resolutions for Webcam test on Win8 bot

BUG= 676041 

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

[modify] https://crrev.com/f824c13d23fd8e7d91887f40d028d112765b73fe/chrome/browser/media/webrtc/webrtc_webcam_browsertest.cc

Status: Fixed (was: Available)
Shouldn't the test be re-enabled before marking this as fixed?
(ah, saw the comment in bug 676020 now).

Sign in to add a comment