newbie-release fails Signing stage |
|||||
Issue descriptionhttps://luci-milo.appspot.com/buildbot/chromeos/newbie-release/1007 " Signing Signing Image signing timed out. " This is fallout from b/72947583
,
Feb 26 2018
Looks like this is happening on fizz, too. https://luci-milo.appspot.com/buildbot/chromeos/fizz-release/1040
,
Feb 26 2018
Oh interesting, this is actually a different issue from what I was thinking. Fallout from b/72947583 triggers this behaviour, from a week ago: https://luci-milo.appspot.com/buildbot/chromeos/newbie-release/1000 The signer fails, but it doesn't timeout, it reports the failure. That's the KI. The fact that the signing step now times out is a different issue however, not sure what's causing it.
,
Feb 28 2018
I discussed this issue with vapier@ and he discovered the following:
the image is bad
sign_android_image.sh: ERROR : Number of re-signed package seems to be wrong
but the signer also ran into a problem when it tried to send an e-mail notification
280218 15:01 INFO: Failed to retrieve access token: { "error" : "deleted_client", "error_description" : "The OAuth client was deleted.",
He's filing a bug to have some other fallback so signing failures are reported instead of showing up as timeouts and I'll link it here when that's ready.
,
Feb 28 2018
(This does mean that this is a bug with the newbie build rather than an infrastructure issue, at any rate. Assigning to norvez@ to take a look.)
,
Feb 28 2018
https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/911905 should fix the "sign_android_image.sh: ERROR : Number of re-signed package seems to be wrong", that's the fallout from b/72947583 But before submitting it I was waiting for the unit tests to be ready (see https://chrome-internal-review.googlesource.com/c/chromeos/cros-signing/+/572073 and following), the previous attempt at a fix broke *all* the signers...
,
Feb 28 2018
,
Mar 2 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/cros-signing/+/1ef8795a6b829034895e6e11ef347b9be30708bd commit 1ef8795a6b829034895e6e11ef347b9be30708bd Author: Nicolas Norvez <norvez@google.com> Date: Fri Mar 02 01:08:30 2018
,
Mar 2 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/cros-signing/+/cf7974d67f346ed15a23803a808a4db683c7a4f9 commit cf7974d67f346ed15a23803a808a4db683c7a4f9 Author: Mike Frysinger <vapier@google.com> Date: Fri Mar 02 01:57:23 2018
,
Mar 2 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/cros-signing/+/6f2f4398d8c4d56e1fadde79c8a3a08dc7bec696 commit 6f2f4398d8c4d56e1fadde79c8a3a08dc7bec696 Author: Nicolas Norvez <norvez@google.com> Date: Fri Mar 02 19:19:34 2018
,
Mar 2 2018
i requeued all the old newbie signer requests and they're all passing, so i guess this is good now |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by osh...@chromium.org
, Feb 23 2018