test: Fix FIT test to pass again
authorSimon Glass <sjg@chromium.org>
Fri, 4 Aug 2017 22:20:16 +0000 (16:20 -0600)
committerTom Rini <trini@konsulko.com>
Sun, 13 Aug 2017 19:17:35 +0000 (15:17 -0400)
A recent change adjusted a test string so that the test no-longer passes.
Fix it.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reported-by: Heiko Schocher <hs@denx.de>
Fixes: b28c5fcc (test-fit.py: Minor grammar/spelling/clarification tweaks)

test/image/test-fit.py

index b0d0538919770e29caf0012f74fa4cfa1ae522fb..ca38f71a15f31a7d62214df69a222620fdf5f6b2 100755 (executable)
@@ -392,7 +392,7 @@ def run_fit_test(mkimage, u_boot):
         fail('Ramdisk loaded but should not be', stdout)
 
     # Find out the offset in the FIT where U-Boot has found the FDT
-    line = find_matching(stdout, 'Booting using the FDT blob at ')
+    line = find_matching(stdout, 'Booting using the fdt blob at ')
     fit_offset = int(line, 16) - params['fit_addr']
     fdt_magic = struct.pack('>L', 0xd00dfeed)
     data = read_file(fit)