Chromium Code Reviews
|
|
Chromium Code Reviews
Issue
1995053002:
Reenable WebRtcBrowserTest.CanForwardRemoteStream on vptr bots. (Closed)
|
Created:
4 years, 7 months ago by krasin Modified:
4 years, 7 months ago Reviewers:
Dirk Pranke CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionReenable WebRtcBrowserTest.CanForwardRemoteStream on vptr bots.
BUG=601957
Committed: https://crrev.com/545143c2d3f0b44e3f2d8c118b7402a13d6db631
Cr-Commit-Position: refs/heads/master@{#394952}
Patch Set 1 #Patch Set 2 : sandbox_linux_unittests on LTO Linux #Messages
Total messages: 24 (11 generated)
The CQ bit was checked by krasin@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1995053002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1995053002/1
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by krasin@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1995053002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1995053002/1
The CQ bit was unchecked by commit-bot@chromium.org
No L-G-T-M from a valid reviewer yet. CQ run can only be started by full committers or once the patch has received an L-G-T-M from a full committer. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
krasin@google.com changed reviewers: + dpranke@chromium.org
CFI trybot shows that the reenabled test passes: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium...
Also reenabled sandbox_linux_unittests on LTO Linux buildbot as the bug was just fixed: https://crbug.com/612507
The CQ bit was checked by krasin@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1995053002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1995053002/20001
lgtm
The CQ bit was unchecked by krasin@google.com
The CQ bit was checked by krasin@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1995053002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1995053002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by krasin@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1995053002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1995053002/20001
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Reenable WebRtcBrowserTest.CanForwardRemoteStream on vptr bots. BUG=601957 ========== to ========== Reenable WebRtcBrowserTest.CanForwardRemoteStream on vptr bots. BUG=601957 Committed: https://crrev.com/545143c2d3f0b44e3f2d8c118b7402a13d6db631 Cr-Commit-Position: refs/heads/master@{#394952} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/545143c2d3f0b44e3f2d8c118b7402a13d6db631 Cr-Commit-Position: refs/heads/master@{#394952} |
