]> code.ossystems Code Review - openembedded-core.git/commit
oeqa/utils/qemurunner: Set both the threadport&serverport with tcpserial parameter
authorKevin Hao <kexin.hao@windriver.com>
Thu, 6 Jun 2019 07:11:47 +0000 (15:11 +0800)
committerArmin Kuster <akuster808@gmail.com>
Fri, 14 Jun 2019 14:05:33 +0000 (07:05 -0700)
commit1ffea0c0fb3688f3cee0a5fa741e969581d01bd3
treed889abd80cbdf97054bf3a0fe20a7c4f2c35cd91
parentdb4b0530841d4d1407b48e262b7255b3f5a186ab
oeqa/utils/qemurunner: Set both the threadport&serverport with tcpserial parameter

After the commit ad522ea6a64e ("runqemu: Let qemuparams override default
settings"), the order of the two "-serial" parameters when running the
qemu have been switched. The effect of this is that the logging thread
will use ttyS1 (of course can't capture the kernel boot message anymore),
and the test command will run on the ttyS0. So the output of the test
command may be mangled by the kernel message (such as call trace), and
let the test command produce a fake timeout error message. We can't fix
it by just adjusting the order of the threadport and serverport, since
it will break some machines such as qemuarm64 which use the virtio
serial. So using the tcpserial to setup both the threadport and
serverport.

[YOCTO Bug 13309]

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
meta/lib/oeqa/utils/qemurunner.py