| Summary: | master] bitbake and hashserve.sock left behind when ^C a build | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Armin Kuster <akuster> |
| Component: | core | Assignee: | Armin Kuster <akuster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | akuster808, JPEWhacker, meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie |
| Version: | 3.1 | ||
| Target Milestone: | 4.1 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Armin Kuster
2019-12-13 18:14:45 UTC
or I get this traceback
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#8)... (Traceback (most recent call last):
File "/home/akuster/oss/maint/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/home/akuster/oss/maint/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
ERROR: Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log)
I think there are 3 problems here: 1) No good timeout for SSTATE_MIRROR 2) Traceback 3) Cleanup after cntl-c I can open additional bugs for the other two. I suspect the files "left behind" still belong to a currently running bitbake server which isn't responsive. Was there bitbake processes left behind from the first Ctrl+C'd build? we will create a new bug for the SSATE_MIRROR time and leave this as is. opened https://bugzilla.yoctoproject.org/show_bug.cgi?id=13716 for the SSTATE_MIRROR issue. This then becomes the cntl-c issue Armin, We've fixed a few Control-C issues, could you check if this is still reproducible or if you prefer, one of us could just move it to 3.6-M1. Is this still a problem? Ping. works for me. |