Error when running testimage
Hi all!
I'm getting this error while running bitbake -c testimage <myimage>:
=====================OERuntimeTestContextExecutor.getControllerModule(target_type, target_modules_path)
*** 0112: target = controller(logger, target_ip,server_ip, **kwargs)
0113: except ImportError as e:
0114: raise TypeError("Failed to import %s from
available controller modules" % target_type)
0115:
0116: return target
Exception: TypeError: __init__() got an unexpected keyword argument 'machine'
=====================
Full logs here: http://paste.ubuntu.com/26119631/
Any ideas on what's going wrong?
TIA,
Alberto
________________________________
This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.
Quoted 18 lines · Alberto
Hi all!
I'm getting this error while running bitbake -c testimage <myimage>:=====================
OERuntimeTestContextExecutor.getControllerModule(target_type, target_modules_path)
*** 0112: target =controller(logger, target_ip, server_ip, **kwargs)
0113: except ImportError as e:
0114: raiseTypeError("Failed to import %s from available controller modules" % target_type)
0115:
0116: return target
Exception: TypeError:__init__()got an unexpected keyword argument 'machine'
=====================
Quoted 3 lines
Full logs here: http://paste.ubuntu.com/26119631/
Any ideas on what's going wrong?
Which MACHINE is this for? It sounds as if the system has no idea how to connect to the machine being tested (e.g. it doesn't know if qemu can be used or what the qemu parameters might be, or if it needs to connect remotely to a machine).
The error message/failure mode certainly needs improving if that is the issue...
Cheers,
Richard
Hi,
Quoted 7 lines · Richard Purdie
Which MACHINE is this for? It sounds as if the system has no idea how to connect to the machine being tested (e.g. it doesn't know if qemu can be used or what the qemu parameters might be, or if it needs to connect remotely to a machine).
The error message/failure mode certainly needs improving if that is the issue...
I had the following line left in conf/local.conf from some previous experiments:
TEST_TARGET = "SystemdbootTarget"
Removing that line fixes the issue. My mistake! :-) Still, it might be a good idea to report a more informative error message in that case.
Ciao,
Alberto
________________________________
This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.