Bug 12367 - moving or removing tmp breaks persistent bitbake server
Summary: moving or removing tmp breaks persistent bitbake server
Status: RESOLVED OBSOLETE
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 4.1 M4
Assignee: Pavel Zhukov
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 13023
  Show dependency tree
 
Reported: 2017-11-20 20:41 UTC by California Sullivan
Modified: 2022-08-26 12:29 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
errors.log (8.75 KB, text/plain)
2017-11-20 20:41 UTC, California Sullivan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description California Sullivan 2017-11-20 20:41:25 UTC
Created attachment 4127 [details]
errors.log

Problem: A number of errors and warnings get spewed if you get rid of tmp after the persistent bitbake server is started, and further bitbake commands don't do anything.

Steps to reproduce:
export BB_SERVER_TIMEOUT=10000
bitbake core-image-minimal
mv tmp tmp-old
bitbake core-image-minimal

Result:
Errors seen in error.log.

Further 'bitbake core-image-minimal' commands result in the following:
[clsulliv@clsulliv build]$ bitbake core-image-minimal
NOTE: Reconnecting to bitbake server...
[clsulliv@clsulliv build]$
Comment 1 Randy MacLeod 2022-06-03 11:54:47 UTC
CCing Pavel who may be interested in making memres more robust.
Comment 2 Pavel Zhukov 2022-08-26 12:29:12 UTC
Looks like the issue is gone (see output below).  Feel free to reopen the bug report if the issue still exists in your environment in master branch.

 $ export BB_SERVER_TIMEOUT=10000
 $ bitbake core-image-minimal 
[ .. output omitted ..]
Build Configuration:
BB_VERSION           = "2.0.1"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
DISTRO               = "poky"
DISTRO_VERSION       = "4.1+snapshot-081a3655fbb10b83793f102b975e153e75240682"
TUNE_FEATURES        = "m64 core2"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       
meta-selftest        = "HEAD:081a3655fbb10b83793f102b975e153e75240682"

[ .. output omitted ..]

NOTE: Tasks Summary: Attempted 3108 tasks of which 3096 didn't need to be rerun and all succeeded.


$ ls
bitbake-cookerdaemon.log  bitbake.lock  bitbake.sock  cache  conf  download  hashserve.sock  sstate-cache  tmp

$ mv tmp tmp-xxx

$ ps aux | grep bitbake
pavel    20103  0.0  0.1 180284 55864 ?        S    14:18   0:00 bitbake-server /mnt/builds/yocto/sources/bitbake/bin/bitbake-server decafbad 3 5 /mnt/builds/yocto/build/build/bitbake-cookerdaemon.log /mnt/builds/yocto/build/build/bitbake.lock /mnt/builds/yocto/build/build/bitbake.sock 10000.0 None 0

$ bitbake core-image-minimal 
NOTE: Reconnecting to bitbake server...
[...omitted...]
Parsing of 935 .bb files complete (0 cached, 935 parsed). 1720 targets, 44 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "2.0.1"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "gentoo-2.8"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
DISTRO               = "poky"
DISTRO_VERSION       = "4.1+snapshot-081a3655fbb10b83793f102b975e153e75240682"
TUNE_FEATURES        = "m64 core2"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       
meta-selftest        = "HEAD:081a3655fbb10b83793f102b975e153e75240682"

[... omitted ...]
Sstate summary: Wanted 1182 Local 1179 Mirrors 0 Missed 3 Current 0 (99% match, 0% complete)

$ ls 
bitbake-cookerdaemon.log  bitbake.lock  bitbake.sock  cache  conf  download  hashserve.sock  sstate-cache  tmp  tmp-xxx


tmp is recreated and bitbake server process is alive