Bug 11836

Summary: [master] nightly-no-x11 barfed
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Armin Kuster <akuster>
Component: coreAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED OBSOLETE QA Contact:
Severity: normal    
Priority: Medium+ CC: meta.mr.watcher, meta.watcher, stephano
Version: 2.4   
Target Milestone: 2.4 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Armin Kuster 2017-07-26 00:53:39 UTC
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..
Comment 2 Richard Purdie 2017-07-30 10:32:21 UTC
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).