Hi Alex, The reason why I changed this is, we have to execute "remote-test-server" on the image through background ssh. So that the "remote-test-server" will be alive waiting for connection. Then in the rust.py control passed to the next command (cmd) for execution. If we use the sshcontrol.py method we have to set a timeout of 600 otherwise default timeout is 300. Even if the test execution completes early due to failure then we have to wait till this timeout.
I tried reducing the timeout to 60 seconds and some of the tests got skipped. If that is ok I will use that copy_to and run from sshcontrol.py as we did in v4 patches and work for the result.output Regards, Vinay On Thu, May 27, 2021 at 5:33 PM Alexander Kanavin <[email protected]> wrote: > > On Thu, 27 May 2021 at 10:11, Vinay Kumar <[email protected]> wrote: >> >> + # To kill remote-test-server executing through >> background ssh >> + killcommand = "kill -9 \$(ps | grep >> remote-test-server | grep -v \"grep\" | awk '{print \$1}')" >> + cmd = cmd + "ssh %s root@%s \"%s\";" % (sshargs, >> qemu.ip, killcommand) > > > I don't think you actually need to kill the remote test server. As qemu will > be stopped anyway, and with it, all the processes that run inside qemu. > > Also, it's better to use cmd only to execute the tests. Starting the server > is better done through SSHControl.run(), and copying the binary via > SSHControl.copy_to() - see examples in selfttest's imagefeatures.py or > runtime_test.py. > > Alex >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#152318): https://lists.openembedded.org/g/openembedded-core/message/152318 Mute This Topic: https://lists.openembedded.org/mt/83120117/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
