maybe a AB issue?? You can also run generated qemu images with a command like 'runqemu qemux86' NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Timeout while attempting to communicate with bitbake server, retrying... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server..
https://autobuilder.yocto.io/builders/nightly-no-x11/builds/370/steps/Running%20Sanity%20Tests/logs/stdio
The logs are gone for this build and the code area has also been reworked with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5f835043f24cef29d229918a9e9cdef62407e558 and preceding patches. We can reopen this if we have any reasonable way to debug this further (or open a new bug for the new issue).