+ shchen (who I think is gardener this week?)

achuith@ is the gardener this week.

Update: The above test failures can also be seen no Latest (Win, Mac & precise64) beta builds, details below:

Link to the builds
==================
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/win%20beta/builds/2372 - Win_beta
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/mac%20beta/builds/2447 - Mac_beta
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/precise64%20beta/builds/2307 - precise64_beta


Link to the log
===============
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/win%20beta/builds/2372/steps/browser_tests/logs/stdio - Win_beta
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/mac%20beta/builds/2447/steps/content_unittests/logs/stdio - Mac_beta
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/precise64%20beta/builds/2307/steps/content_unittests/logs/stdio - precise64_beta

Thank you!

Please try to resolve this issue ASAP as we're very close to Desktop-M50 Stable candidate cut.

Removing Stable blocker label based on update #8 in  issue 599222 . But please try to fix ASAP.

Still failing: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/Linux%20ChromeOS%20Buildspec%20Tests/builds/607

sorry devtools folks - you've heard a lot from me this week.

Any idea why these browser tests are failing?

This is due to this merge: https://codereview.chromium.org/1855363002/. We didn't merge test changes as it was hard to do (different baselines). All tests should be passing on trunk bots.

I had an impression that nobody pays attention to test failures on the branch builds. Is that not a case anymore? Anyway, merging test fixes seems unnecessary.

#11: The Chrome OS TE team watches them quite closely, as we depend on browsertests in a branch build to supplement (and in many cases replace) manual testing of that official release candidate.

#11: Same is the case from "Chrome Desktop TE" as well.

Good to know! We'll be more careful with merging tests in the future.

What is the resolution of this bug? Have the test fixes been merged?

Would like to land a CL to disable these tests in M50. A merge of the fixes is not possible. 

This affects tests only - no production code.

[Automated comment] Less than 2 weeks to go before stable on M50, manual review required.

tinazh@ can you please approve for M50? We would like to get this bot green really quickly.

Hey, what's the proposed CL?

Here is the patch which disables a bunch of tests in 2661 branch: https://codereview.chromium.org/1879803002/

Approving merge to M50.

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

commit 0c1086779e2dc5b1303595d86552448e5143428e
Author: Dmitry Gozman <dgozman@chromium.org>
Date: Tue Apr 12 18:29:02 2016

Disable a bunch of DevTools browsertests in 2661.

BUG= 600791 
R=achuith@chromium.org
TBR=achuith@chromium.org

Review URL: https://codereview.chromium.org/1879803002 .

Cr-Commit-Position: refs/branch-heads/2661@{#566}
Cr-Branched-From: ef6f6ae5e4c96622286b563658d5cd62a6cf1197-refs/heads/master@{#378081}

[modify] https://crrev.com/0c1086779e2dc5b1303595d86552448e5143428e/chrome/browser/devtools/devtools_sanity_browsertest.cc

Thank you Dmitry

bulk verify (M50 clean up)