Speculative revert by sheriff

Speculative revert by sheriff

I am reverting all CLs that could have caused this failure:

http://build.chromium.org/p/chromium.linux/builders/
    Android%20Tests%20%28dbg%29/builds/27276

I will start re-landing vindicated CLs shortly.

Revert "Convert a11y_page.css to a11y_page_style.html. See http://goo.gl/vIGSCO for more information."

This reverts commit eb48d65705e44b80d1d7a3b4f21c567802c102bb.

Revert "Supply build properties to run-bisect-perf regression for android bisects."

This reverts commit 9d70bb94984b02c17678ccf482d1a7b7c760a43f.

Revert "[cros New-GAIA] Webview login and new GAIA endpoint enabled by default"

This reverts commit 29061783f8b59f1e78286a87a3bb7d18129f639a.

Revert "Prime the landing pad for the new video rendering pipeline."

This reverts commit 45a3c93f745eabf6c1b1cbdac87ed4350a919e76.

Revert "Implement separate error dialog for cws widget container"

This reverts commit 7ed1f876f6f4d79ac074b25f2066d514603aa18d.

Revert "Create device_bluetooth watchlist; add scheib."

This reverts commit 40514c99cd45d1c8e9caef3245d42533d9810179.

Revert "Convert checkbox.css to checkbox_style.html. See http://goo.gl/vIGSCO for more information."

This reverts commit a687f31a786645508622482e9033f497364a43cd.

Revert "Created new URLRequestContext for secure proxy check."

This reverts commit 652eabf1141c00594aa6e9ed81beb980aec89198.

Revert "Revert of Fix scroll regression when specifying an extension id. (patchset #4 id:60001 of https://codereview.chromium.org/1064573003/)"

This reverts commit 488846cd562f444831982d82ef0bc9ca0dd79028.

Revert "Sync: Add Android test for downloading a bookmark"

This reverts commit 9c052713563111ac3d6cc64d4b5cfdfa27c202f4.

Revert "ScreenOrientationController to start observing even without an internal display."

This reverts commit 31fed68a524d49f99cebf02dca6ad49019e9900c.

Revert "Fix MB configurations for Mac and Win GN bots."

This reverts commit 31a66f3e705d20a39033a7b7d7f09a60517e6b9d.

Revert "Add tool/perf/measurements path to check for CQ jobs."

This reverts commit 99e1ac1d217174dad7a862f6a0fc44950d503737.

Revert "Implement Notification.data for persistent notifications."

This reverts commit 539f51d6af62097059c34b1c19dfbc4352413ad7.

Revert "Fix playback rate calculations for WallClockTimeSource."

This reverts commit 3ec02d642465872d9ab7d7db600d0480a57b3cab.

Revert "Roll src/third_party/pdfium eddab44:b330016"

This reverts commit 81d51e253cfacd5648cca9f12b605e63971a9ab1.

Revert "cc: Make DisplayItemList::Append replay into an SkPicture"

This reverts commit ec7c07e57bc5f91e3ba0bdeba8b6f534978615b0.

Revert "Clean up URLFetcher unit tests, part 5."

This reverts commit 8eeb3bf4a02be612cacb3cdbb5c223d909939527.

BUG=None
TBR=akuegel

Committed: https://chromium.googlesource.com/chromium/src/+/919dce4400651813d5ff6e8a85b944a5987adcb7

[commit-bot: I haz the power, 2015-04-16 10:13:11]

Patchset 2 (id:??) landed as
https://crrev.com/919dce4400651813d5ff6e8a85b944a5987adcb7
Cr-Commit-Position: refs/heads/master@{#325411}

[bartfab (slow), 2015-04-16 10:13:24]

Committed patchset #2 (id:20001) manually as
919dce4400651813d5ff6e8a85b944a5987adcb7 (tree was closed).

[Lei Zhang, 2015-04-20 21:01:50]

I know sheriffs usually shoot and ask questions later, but a massive revert like
this is going a bit over the top. Did you notify the authors of all the reverted
CLs? Did you ever figure out who was actually to blame for the failures?

[bartfab (slow), 2015-04-21 08:45:18]

On 2015/04/20 21:01:50, Lei Zhang wrote:
> I know sheriffs usually shoot and ask questions later, but a massive revert
like
> this is going a bit over the top. Did you notify the authors of all the
reverted
> CLs? Did you ever figure out who was actually to blame for the failures?

I did not need to notify anyone because I immediately reverted the revert:

https://codereview.chromium.org/1094553002

This revert was necessary because one of the 19 CLs caused breakage on the
Android bots and neither I nor the troopers could figure out which one. The
breakage happened on waterfall bots only, so the plan was to do a series of
speculative reverts/re-lands to bisect and figure out the broken commit. Just as
I was starting this process, an Android developer jumped in with more
information and we figured out the offending CL. Thus, I was able to quickly
reland.