This builder always fails the signer test because kernel parameters don't matching the signing requirements.
https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-generic-goofy-release/builds/284/steps/SignerTest/logs/stdio
ERROR security_test_image: sane_lsb-release: test failed
INFO security_test_image: Running ensure_secure_kernelparams.sh
Kernel dm= parameter does not match any expected values!
Actual: 1 vroot none ro 1,0 4096000 verity payload=PARTUUID=%U/PARTNROFF=1 hashtree=PARTUUID=%U/PARTNROFF=1 hashstart=4096000 alg=sha1 root_hexdigest=0a32d7caf2b84b5c200ebf2b7cb4f23b90e3af4d salt=ab8650ca539c69d9f7340862a65c47d8bc3ee7044b228454d9b7ee04e0aba371
Expected:
Expected (regex):
Unexpected kernel parameters found:
console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 noinitrd vt.global_cursor_default=0 kern_guid=%U add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Comment 1 by shuqianz@chromium.org
, May 9 2016