And Mac10.11 (dbg):
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Mac10.11%20%28dbg%29/builds/11037

This is the same thing that happened in crbug.com/770238

Reverting...
https://chromium-review.googlesource.com/c/chromium/src/+/794152

Issue 789233 has been merged into this issue.

This is failing again on Mac10.12:

https://uberchromegw.corp.google.com/i/chromium.mac/builders/Mac10.12%20Tests/builds/7776

That looks likely to be the same problem :(.

actually, no. I'm not sure why that step took that long.

It looks like one of the upload copy steps timed out, but the amount of data looks comparable to the previous and subsequent builds, both of which complete in ~10 min. 

Perhaps this was some sort of cloud storage transient failure ...

Dirk, is there action to be taken here, or should we just close this?

It looks like it shouldn't be P1, or in the sheriff queue, for now.

It looks like this is failing about 1 out of every 50 builds. It's unclear why, though.

I think there's definitely more to do here. +martiniss, who has been looking at similar issues recently.

But, this isn't a trooper thing, more a regular issue needing work.

Each failure is because the archive step hangs and doesn't print anything to stdout so the the build gets killed:
"command timed out: 2400 seconds without output, attempting to kill"

 bug 792737  is on file to make this step not take so long; duping into that