sumo/ninja failing to sign due to maxcpus=2 |
||||||||
Issue description220417 14:48 DEBUG: RunCommand: /cros/vboot_reference/scripts/image_signing/ensure_secure_kernelparams.sh /tmp/signer.m6RkH1/recovery_image.bin /cros/security_test_baselines/ensure_secure_kernelparams.config 220417 14:48 DEBUG: (stdout): Unexpected kernel parameters found: maxcpus=2
,
Apr 24 2017
example fix: https://chrome-internal-review.googlesource.com/338095
,
Apr 24 2017
,
Apr 24 2017
I have a confirmed fix. Patch is on its way.
,
Apr 24 2017
Patch is uploaded for review. https://chrome-internal-review.googlesource.com/c/360789/
,
Apr 24 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/cros-signing/+/0c60c3ea8b223a5e46412446ab1a9d009d840529 commit 0c60c3ea8b223a5e46412446ab1a9d009d840529 Author: Chad Versace <chadversary@chromium.org> Date: Mon Apr 24 23:19:03 2017
,
Apr 25 2017
,
May 24 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/cros-signing/+/09915639cda96f272ea618af4cc249453451d9d2 commit 09915639cda96f272ea618af4cc249453451d9d2 Author: Chad Versace <chadversary@chromium.org> Date: Wed May 24 20:55:11 2017
,
May 24 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/cros-signing/+/09915639cda96f272ea618af4cc249453451d9d2 commit 09915639cda96f272ea618af4cc249453451d9d2 Author: Chad Versace <chadversary@chromium.org> Date: Wed May 24 20:55:11 2017
,
May 30 2017
,
Aug 1 2017
,
Aug 3 2017
Closing. Please reopen it if its not fixed. Thanks! |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by vapier@chromium.org
, Apr 24 2017