| Summary: | strange build failure with no output | ||
|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Jussi Kukkonen <jku> |
| Component: | general | Assignee: | Mariano Lopez <mariano.lopez> |
| Status: | VERIFIED FIXED | QA Contact: | Cristina Agurida <cristina-danielax.agurida> |
| Severity: | normal | ||
| Priority: | High | CC: | benjamin.esquivel, bogdanx.a.voiculescu, mariano.lopez, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 1.9 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | |||
| Bug Blocks: | 8249 | ||
|
Description
Jussi Kukkonen
2015-09-02 07:58:37 UTC
There are two parts to this. It took 12 minutes since it was running chmod -st -R in the environment setup script. Bitbake was actually exiting immediately and should have said bitbake.lock couldn't be acquired. The -w option to bitbake has a bug and was preventing this from being shown. The chmod -st -R issue is fixed with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d8caef4f6e38efb739866a1de38f3bae8f1754ed There is a bitbake patch for the missing error message. The reason bitbake.lock is being held is that the autobuilder tried to kill a previous task yet the runqemu process remained. We likely need to improve the SIGTERM handling there to ensure that does get killed. The bug should likely remain open until this last issue is resolved. A likely good reproducer for this is "bitabke -c testimage core-image-sato", then Ctrl+C it after qemu starts and notice that qemu remains running. We need to fix it so qemu exits. Sent patch to the list to get the SIGTERM in testimage class This has been solved with the following commits: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=6271fcb5896464d0c71172b02de548195191abf8 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=6b41b7cc323e3bed2d0545019e7bdc8e006db1e9 Verified on master: a9053ac0829eb01f6f002587854d01e47a78e6f0 |