"WebRtcGetUserMediaBrowserTest.TraceVideoCaptureControllerPerformanceDuringGetUserMedia" is flaky |
|||||||
Issue description"WebRtcGetUserMediaBrowserTest.TraceVideoCaptureControllerPerformanceDuringGetUserMedia" 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 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyYQsSBUZsYWtlIlZXZWJSdGNHZXRVc2VyTWVkaWFCcm93c2VyVGVzdC5UcmFjZVZpZGVvQ2FwdHVyZUNvbnRyb2xsZXJQZXJmb3JtYW5jZUR1cmluZ0dldFVzZXJNZWRpYQw. 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
,
Aug 4 2016
Detected 3 new flakes for test/step "WebRtcGetUserMediaBrowserTest.TraceVideoCaptureControllerPerformanceDuringGetUserMedia". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyYQsSBUZsYWtlIlZXZWJSdGNHZXRVc2VyTWVkaWFCcm93c2VyVGVzdC5UcmFjZVZpZGVvQ2FwdHVyZUNvbnRyb2xsZXJQZXJmb3JtYW5jZUR1cmluZ0dldFVzZXJNZWRpYQw. This message was posted automatically by the chromium-try-flakes app.
,
Aug 9 2016
Seems to be failing on: [FATAL:webrtc_getusermedia_browsertest.cc(122)] Check failed: !has_more_events.
,
Aug 10 2016
,
Aug 10 2016
The failures are now too old to view the logs. alancutter@, it would have been useful to paste a whole backtrace for this.
,
Aug 10 2016
Since the test is disabled, all that remains is to assign it to someone for investigation. phoglund@, can you PTAL or direct it towards the team/person that should?
,
Sep 16 2016
Miguel, I believe you wrote this one? Care to take a look? If you don't have time, I think we can live with having this test off on Android, at least to the next fixit (in that case, WontFix the bug).
,
Sep 21 2016
#7: I don't think I'll have the time, specially with no logs around. It could be flaky under the emulator too. In any case marking won't fix.
,
Jan 24 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by bugdroid1@chromium.org
, Aug 4 2016