This bug requires manual review: Reverts referenced in bugdroid comments after merge request.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), bhthompson@(cros), govind@(desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Seems reasonable to me as a revert, we would like to get this in for the next dev for Chrome OS (build next Monday evening) if possible due to the high crash rate.
Since this impacts other platforms I'll defer to Krishna for approval.
If we cannot revert in 58 can we get a Chrome branch for Chrome OS to use for a new Dev tomorrow?
Dev on Chrome OS is currently at ~10x beta/stable crash wise, and this is causing ~70% of them.
Philippe, given this merged over a day ago and this is causing some nasty crashes on CrOS, if you believe the revert to be safe at this point please go ahead and merge into R58.
If at all possible we would like to land this afternoon so we can get a new Chrome for Chrome OS built for a new dev tomorrow.
I am not familiar with the merge procedure.
http://www.chromium.org/developers/how-tos/drover mentions that I need to be a committer. Can I still do the merge without being a committer?
Also, I am busy teaching a seminar this PM, so I can try to do this during the break, but if it is time sensitive and someone else can take care of it, it might go more smoothly.
Comment 1 by bugdroid1@chromium.org
, Mar 7 2017