[poky] What's taking so long??
Richard Purdie
richard.purdie at linuxfoundation.org
Fri Jan 21 06:14:18 PST 2011
On Thu, 2011-01-20 at 09:40 -0700, Gary Thomas wrote:
> Note: I got tired of waiting for this (I needed to rebuild
> anyway) and typed ^C. I got this dump which I don't understand:
>
> NOTE: Sending SIGTERM to remaining 1 tasks
> Warning, worker left partial message: <event>(ilogging
> LogRecord
> p1
> (dp2
> S'taskpid'
> p3
> I23606
> sS'threadName'
> p4
> S'MainThread'
> p5
> sS'name'
> p6
> S'BitBake'
> p7
> sS'thread'
> p8
> I-1216357584
> sS'created'
> p9
> F1295541481.8053031
> sS'process'
> p10
> I23606
> sS'processName'
> p11
> S'MainProcess'
> p12
> sS'args'
> p13
> (tsS'module'
> p14
> S'__init__'
> p15
> sS'filename'
> p16
> S'__init__.py'
> p17
> sS'levelno'
> p18
> I20
> sS'exc_text'
> p19
> NsS'pathname'
> p20
> S'/home/local/poky-amltd/bitbake/lib/bb/__init__.py'
> p21
> sS'lineno'
> p22
> I85
> sS'msg'
> p23
> S' /kernel/arch/arm/plat-s3c64xx/dev-audio.c'
> p24
> sS'exc_info'
> p25
> NsS'funcName'
> p26
> S'note'
> p27
>
> What does it mean? Maybe it helps understand the problem.
Its the internal representation of what you see as messages on the
bitbake console (output of a pickled LogRecord). The worker didn't
complete its queue so there was a partial message, it doesn't help work
out where the time is being spent sadly.
Cheers,
Richard
More information about the poky
mailing list