summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2019-10-28 16:52:08 -0700
committerCommit Bot <commit-bot@chromium.org>2019-11-02 07:22:13 +0000
commit01cc9b7c64b486017f96829e5f374fbd3bdbf15a (patch)
tree699237c32ece112ac98555e28738c9cf961555dd
parent8e8f4b990e8ae15a493043878115df099173414d (diff)
downloadvboot-01cc9b7c64b486017f96829e5f374fbd3bdbf15a.tar.gz
tests: Update futility show expected test output
If you read the manpage for printf *really* closely, it seems that the %#x token only prints the 0x prefix for non-zero values. Huh... never knew that (and our firmware implementations in fact don't honor that, but glibc does). Anyway, I think we're fine with either behavior but this broke the expected output for one of our futility tests, which this patch fixes (originally broken in CL:1840191). BRANCH=None BUG=None TEST=make runtests Change-Id: Id54ff6f56e02333ab01b09b75deb16f47da01bc3 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/1885411 Reviewed-by: Joel Kitching <kitching@chromium.org>
-rw-r--r--tests/futility/expect_output/show.tests_futility_data_kern_preamble.bin2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/futility/expect_output/show.tests_futility_data_kern_preamble.bin b/tests/futility/expect_output/show.tests_futility_data_kern_preamble.bin
index d1ceb039..359f45ca 100644
--- a/tests/futility/expect_output/show.tests_futility_data_kern_preamble.bin
+++ b/tests/futility/expect_output/show.tests_futility_data_kern_preamble.bin
@@ -14,7 +14,7 @@ Kernel Preamble:
Body size: 0x12000
Bootloader address: 0x10a000
Bootloader size: 0x8000
- Flags: 0x0
+ Flags: 0
Body verification succeeded.
Config:
hi there