We will have an ability to specify COM STA task runners soon.

How do you feel about https://codereview.chromium.org/2774653003 in the meanwhile?

By looking at b/36221111, this seems to be an M57 regression but specific to HP printers. How many users are impacted by this? Please note that M57 for desktop has been out for stable at 1% of users since last two weeks (starting 03/09).

Please plan to have fix landed/merged to M57 release branch by 5:00 PM PT, tomorrow Friday, 03/24 so we can pick it up for next week Stable release if this is indeed a stable blocker. Thank you.

Other printers may be affected. We don't know for sure. I'll try to get the fix landed / merged ASAP.

I have CLs prepped for merging.
M57: https://codereview.chromium.org/2765333004
M58: https://codereview.chromium.org/2772573004

Thank you  thestig@.
Cl is not yet landed in Canary. Will it be a safe to directly merge to release branch (M57 and M58) without Canary coverage?

CL is in CQ and should land shortly. Not sure if it will make a Canary build in time for testing tomorrow. I've tested the M57 version locally. It is service process code, so it only affects the Cloud Print Connector.

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

commit d36381e3b65747fc7ea9df344129fa7ced3a0afe
Author: thestig <thestig@chromium.org>
Date: Fri Mar 24 03:26:36 2017

Initialize COM STA in the service process.

BUG= 704754 

Review-Url: https://codereview.chromium.org/2774653003
Cr-Commit-Position: refs/heads/master@{#459353}

[modify] https://crrev.com/d36381e3b65747fc7ea9df344129fa7ced3a0afe/chrome/service/service_process.cc

Cl listed at #8 didn't make it today's canary cut 8:00 PM PT.
As it is service process code only affects the Cloud Print Connector, we don't expect to see any functional/stability regression, correct?

Correct. Nothing else should be affected by this. I can do my own official build tomorrow at ToT and verify it works there too.

Thank you  thestig@. Please update the bug once you verify it works in ToT tomorrow. I will approve M57 merge then. Please plan for M57 merge before 5:00 PM PT.

Thanks for digging into this, let us know if it doesn't merge cleanly in M57.

gab: It doesn't merge cleanly, but I have the branch-specific CLs ready in comment 5. Doing a built at ToT now to verify.

Well, the bad news is ToT builds are broken for a different reason, so I can't actually verify.

That is to say, Canary, without r459353 is broken too - printers aren't registering at all.

Though I have tested M57 locally and I know it works. So in the interest of time, I'll request a merge now. We'll get a new M57 build with the merge and I will verify that works.

Approving merge to M57 based on comment #9, #10 and #16. Please merge ASAP. Thank you.

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

commit a30e61fe2c335554a3287313485e82d6bfe0b271
Author: Lei Zhang <thestig@chromium.org>
Date: Fri Mar 24 21:12:23 2017

M57: Initialize COM STA in the service process.

BUG= 704754 

Review-Url: https://codereview.chromium.org/2765333004 .
Cr-Commit-Position: refs/branch-heads/2987@{#876}
Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}

[modify] https://crrev.com/a30e61fe2c335554a3287313485e82d6bfe0b271/chrome/service/service_process.cc

Cool thanks, CL looks pretty similar to me so I guess conflict was minor?

Minor indeed. It conflicted with r458450.

59.0.3048.0 + r459353 works for me. Will verify the next M57 build when it's ready.

Filed  bug 705175  for the printer registration problem that is preventing verification on ToT. After verifying for M57, I will also request a merge to M58.

M57 build #57.0.2987.127 is available with this fix for testing.

Please request a merge to M58 as well if change looks good in M57. Thank you.

We tested 57.0.2987.128 and the offline cloud printer issue no longer occurs.

Your change meets the bar and is auto-approved for M58. Please go ahead and merge the CL to branch 3029 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)

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

Your change is approved for M58. Please merge ASAP so that it will be picked up for next Beta Release, RC cut on (Tuesday-03/28) at 4.00 PM PST.

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

commit 7609c1d6cc0485f6c03dd22572be811bd0212d39
Author: Lei Zhang <thestig@chromium.org>
Date: Mon Mar 27 18:04:14 2017

M58: Initialize COM STA in the service process.

BUG= 704754 

Review-Url: https://codereview.chromium.org/2772573004 .
Cr-Commit-Position: refs/branch-heads/3029@{#432}
Cr-Branched-From: 939b32ee5ba05c396eef3fd992822fcca9a2e262-refs/heads/master@{#454471}

[modify] https://crrev.com/7609c1d6cc0485f6c03dd22572be811bd0212d39/chrome/service/service_process.cc