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

Issue 835224 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , iOS , Chrome , Mac , Fuchsia
Pri: 1
Type: Bug



Sign in to add a comment

Merge probe trigger test and bugfix to M67.

Project Member Reported by philipel@chromium.org, Apr 20 2018

Issue description

A performance regression fix (https://bugs.chromium.org/p/chromium/issues/detail?id=834255) and an end-to-end test related to the new probe trigger needs to be merged to M67.

https://webrtc-review.googlesource.com/c/src/+/64822
https://webrtc-review.googlesource.com/c/src/+/70760
 
Description: Show this description
Description: Show this description
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 21 2018

Labels: -Merge-Request-67 Merge-Approved-67 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M67. Please go ahead and merge the CL to branch 3396 manually. Please contact milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by gov...@chromium.org, Apr 21 2018

Pls merge your change to M67 branch 3396 by 1:00 PM PT, Monday (04/23) so we can pick it up next M67 Dev/Beta release. Thank you.

Comment 6 by gov...@chromium.org, Apr 24 2018

Labels: -Merge-Approved-67 merge-merged-67
Per comment #5, this is already merged to M67.
[bulk-edit: disregard if N/A] Can the owner please set milestone to this bug if applicable?

Sign in to add a comment