A failure on the autobuilder made me notice that the tests for SSH logins are touching the user's ~/.ssh/known_hosts file: https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/67/steps/Running%20oe-selftest/logs/stdio We should *never* be writing to user configuration files like this. Probably the easiest alternative is to pass "-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no" as we do in the oe-selftest tests for devtool.
Hi Paul, I updated the testcases as you suggested. Also the testcases now determine the qemu ip address dynamically in order to be able to ssh into it, so they don't assume 192.168.7.2 any more. --Daniel
Code review is needed.
Waiting for code review.
Fixed in oe-core f58df3a630b774083934171463b2b07add29dc0e.
Hello, Checked for last version of test cases in master (839fb1893546ad58a1f5475a9e852b81afb056d6) under poky/meta/lib/oeqa/selftest/imagefeatures.py and no ssh command touches any file from ~/.ssh Marking as verified.