Bug 8632

Summary: Boot timeout on nightly-qa-systemd
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: coreAssignee: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Status: VERIFIED WONTFIX QA Contact: Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu>
Severity: normal    
Priority: Medium CC: bogdanx.a.voiculescu, meta.mr.watcher, meta.watcher
Version: 2.0   
Target Milestone: 2.1   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Leonardo Sandoval Gonzalez 2015-11-03 14:33:34 UTC 
One of the nightly-qa-systemd runs on the AB [1] failed and apparently the qemu image took longer that the defined timeout time, so at some point the AB kicked out the build. To avoid build folder removal, the folder was moved to [2] on the proper slave machine

[1] https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/523
[2] /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-qa-systemd-archive/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/testimage
Comment 1 Leonardo Sandoval Gonzalez 2015-11-06 16:28:26 UTC 
This problem most probably happened due to a high system load. With the introduced commit [1] which IO tasks can be prioritized, it fixed the problem indirectly. 

In case the problem presents in the future, it should be analyzed further.


[1] http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=290534d3ff53b3c0a50e480863474d1785088c5a
Comment 2 Bogdan Alexandru Voiculescu 2015-11-17 10:18:50 UTC 
nothing to investigate; timeout will not be increased.