I'm not really familiar with this, Michael or Di should be able to help here.

What error are we talking about in that trigger output? It looks like it worked just fine, and created the buildspec and triggered the build as expected. If there's a problem, it was somewhere else. I seem to recall there were some official Win compile failures last night, so maybe this was one of them?

Looks like the build failed to upload, although for some reason it didn't actually cause the step to fail:

https://uberchromegw.corp.google.com/i/official.desktop/builders/win-asan/builds/537/steps/shell/logs/stdio

The errors are a little weird there, both an AccessDeniedException and invalid_grant, which I've never seen before. Since the other builders worked, even on later builds, I think it might have been a temporary cloud storage issue. If we still wabt an ASAN canary, I'd suggest kicking a new one.

Or actually, since that build compiled successfully but never uploaded anything, this is one of the few instances where we could just press the "rebuild" button on the builder. I'll see if that works.

FYI, finally catching up on all of last night's email, I see:

  "PSA: All waterfalls are purple due to a credentail issue."

I strongly suspect that was the cause of the upload problems.

The build succeeded this time:
https://uberchromegw.corp.google.com/i/official.desktop/builders/win-asan/builds/538