tree affbd6f4b529ad5153af185344820b7e515372f6
parent c148618e07fe0d18f84bdf4200cdd7278d9cc731
author Yicheng Li <yichengli@chromium.org> 1579205365 -0800
committer Commit Bot <commit-bot@chromium.org> 1580500078 +0000

cros/faft: Add statically built futility

Some faft tests rely on futility to re-sign firmware images with
dev keys. However, futility is not available in the base container
used on lab servers. Add statically built futility so that these
tests can run on lab servers.

futility in this change was built in the following way:
(In chroot)
cd ~/trunk/src/platform/vboot_reference
(Open Makefile)
(Remove -Wimplicit-fallthrough from COMMON_FLAGS)
(Remove the line "${FUZZ_TEST_BINS}: LDFLAGS += -fsanitize=fuzzer")
rm -rf build && make STATIC=1 futil -j

BUG=chromium:961293, chromium:1003023
TEST=test_that --board=nocturne <IP> suite:fingerprint
TEST=(In chroot) cd ~/trunk/src/third_party/autotest
     tar -cvjSf autotest_server_package.tar.bz2 \
         --exclude "files/ExternalSource" --exclude "files/site-packages" \
	 --exclude "files/client" files/
     (Copy the resulting tarball to base container's /usr/local
      and extract there)
     (Copy nocturne_fp_v2.2.191-1d529566e.bin to container's /usr/local)
     (In base container) cd /usr/local/files/server/cros/faft
     ./gen_test_images.sh nocturne_fp \
         /usr/local/nocturne_fp_v2.2.191-1d529566e.bin

Change-Id: I75ab466b4f85c8bb96e698d1d48f6691ecd63735
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2006017
Reviewed-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Tested-by: Yicheng Li <yichengli@chromium.org>
Tested-by: Tom Hughes <tomhughes@chromium.org>
Commit-Queue: Tom Hughes <tomhughes@chromium.org>