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

Issue 875545 link

Starred by 1 user
Status: WontFix
Owner:
sande...@chromium.org
Closed: Aug 21
Cc:
w...@chromium.org
█ emadomara@chromium.org
webrtc-network-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"RTCVideoDecoderAdapterTest.Decode_Error" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Aug 18 
"RTCVideoDecoderAdapterTest.Decode_Error" 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 21 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMgsSBUZsYWtlIidSVENWaWRlb0RlY29kZXJBZGFwdGVyVGVzdC5EZWNvZGVfRXJyb3IM.

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

Comment 1 by apaci...@chromium.org, Aug 20

Cc: w...@chromium.org
Labels: -Pri-1 -Sheriff-Chromium Pri-2
Owner: sande...@chromium.org
Status: Assigned (was: Untriaged)
+sandersd OWNER, +wez looking into root cause

These tests were reenabled and currently expected to be flaky.

Dropping pri since this bug is for monitoring purposes.

Comment 2 by jsb...@chromium.org, Aug 20 

Dupe of  issue 875278  ?

Comment 3 by w...@chromium.org, Aug 20

Components: Internals>WebRTC
Labels: -Pri-2 M-70 Pri-1
Re #2: The test was re-enabled after fixing the two [known] TaskScheduler leaks, though.  I'll see if we can get something landed as per gab@'s suggestion on issue 875486, to try to catch TaskScheduler-leaking tests in general, rather than keep whacking at moles.

For this particular flake, I'm running the suite locally to see if I can repro & get a crash stack to confirm one way or the other, and we should have working crash-stacks on Fuchsia again later today ( issue 875113 ).

Bumping up priority, since flakes lead to CQ-rage.

Comment 4 by w...@chromium.org, Aug 21

Status: WontFix (was: Assigned)
Following the flakes link in this report, all flakes are prior to https://chromium-review.googlesource.com/c/chromium/src/+/1180408 landing.
►

Sign in to add a comment