Bug 9098 - Bitbake stalls when pressing Ctrl+C during parsing recipes phase
Summary: Bitbake stalls when pressing Ctrl+C during parsing recipes phase
Status: VERIFIED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.1 M3
Assignee: Ed Bartosh
QA Contact: Alexandru Georgescu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-02-11 10:58 UTC by Costin
Modified: 2016-03-07 07:06 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Costin 2016-02-11 10:58:28 UTC
Hello,

Test done on Ubuntu 15.10.

On latest master, 7cd835177ae  while trying to build core-image-* the environment stalls when pressing Ctrl+C during parsing recipes stage:
cosscat@ubnt:/media/yp_builds/poky/build$ MACHINE=genericx86-64 bitbake core-image-sato-sdk 
Parsing recipes:  60% |######################################################################################################                                                                  | ETA:  00:00:05
Keyboard Interrupt, closing down...

ERROR: Timeout while attempting to communicate with bitbake server

the only way to stop it is by killing the resulted processes:
cosscat@ubnt:~$ for i in $(ps -eaf | grep bitbake | awk '{print $2}'); do  kill -9 $i; done



For an older commit, 34e95b034904 it used to work fine.
cosscat@ubnt:/media/yp_builds/poky/build$ bitbake core-image-sato 
Parsing recipes:  30% |###################################################                                                                                                                     | ETA:  00:00:15
Keyboard Interrupt, closing down...

WARNING: Cooker received SIGTERM, shutting down...

Summary: There was 1 WARNING message shown.
Execution was interrupted, returning a non-zero exit code.
Comment 2 Alexandru Georgescu 2016-03-07 07:06:54 UTC
Verified with latest masteR: bd3a1d5bddeab2b327055a61e85423303327fc09