On 10/11/2018 03:57 AM, Bin Meng wrote:
Hi Heinrich,
On Thu, Oct 11, 2018 at 9:48 AM Bin Meng bmeng.cn@gmail.com wrote:
Add qemu-x86_64 to the list of targets we use for test.py runs.
Signed-off-by: Bin Meng bmeng.cn@gmail.com
testp.py testing is currently failing at 'bootefi selftest'.
Can you try this series for the 'bootefi selftest' testing?
I am clueless why the EFI subsystems is failing completely on qemu-x86_64_defconfig.
Any printf() or puts() statement I put into lib/efi_loader/efi_boottime.c leads to no output at all.
I connected gdb with
gdb u-boot -ex 'target remote localhost:1234' add-symbol-file u-boot <relocaddr>
But the debugger did not stop at breakpoints.
Regards
Heinrich
BTW: do you know how to call test.py on the local machine to do testing on QEMU? The doc does not provide enough information ..
.travis.yml | 8 ++++++++ 1 file changed, 8 insertions(+)
diff --git a/.travis.yml b/.travis.yml index 2b759c9..9d0531f 100644 --- a/.travis.yml +++ b/.travis.yml @@ -408,6 +408,14 @@ matrix: BUILDMAN="^qemu-x86$" TOOLCHAIN="x86_64" BUILD_ROM="yes"
- name: "test/py qemu-x86_64"
env:- TEST_PY_BD="qemu-x86_64"TEST_PY_TEST_SPEC="not sleep"QEMU_TARGET="x86_64-softmmu"BUILDMAN="^qemu-x86_64$"TOOLCHAIN="x86_64"BUILD_ROM="yes"
- name: "test/py zynq_zc702" env:
- TEST_PY_BD="zynq_zc702"
--
Regards, Bin