From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: What's taking so long??
Date: Fri, 21 Jan 2011 16:17:37 +0000 [thread overview]
Message-ID: <1295626657.14388.31197.camel@rex> (raw)
In-Reply-To: <4D399769.1050803@mlbassoc.com>
On Fri, 2011-01-21 at 07:25 -0700, Gary Thomas wrote:
> This particular test was isolated, just that one recipe. I noticed
> it before when building a complete image, so running it isolated does not
> seem to make any difference. There is also nothing else running on my build
> machine (it's a separate server that is used only for builds)
>
> This is against master as of 2011-01-14 (897530621fabf3c345c302050a5c21e16097a2ba)
> with my local layers.
>
> What can I look at (alternatively what data can I provide) to help
> understand this?
You could try pulling in:
http://git.pokylinux.org/cgit.cgi/poky/commit/?id=ede381d56b180b384fdad98d445e5430819cfade
http://git.pokylinux.org/cgit.cgi/poky/commit/?id=7857834691868b7f48f732ee78d8770f5473ff68
http://git.pokylinux.org/cgit.cgi/poky/commit/?id=fd88588df029604689db9b0e30c55aad68392a5d
and see if they fix the problem. I'm not sure that they would in a
single task case but who knows. You could also try adding timings as per
my previous email, the change to package.bbclass was simply:
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 8e7fa26..8b0cb96 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -1082,6 +1082,7 @@ python package_do_package () {
return
for f in (bb.data.getVar('PACKAGEFUNCS', d, True) or '').split():
+ bb.error("Running %s" % f)
bb.build.exec_func(f, d)
}
do_package[dirs] = "${SHLIBSWORKDIR} ${PKGDESTWORK} ${D}"
as I'd like to understand of the 23 minutes, where the time is being spent.
Cheers,
Richard
next prev parent reply other threads:[~2011-01-21 16:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 15:11 What's taking so long?? Gary Thomas
2011-01-20 15:58 ` Joshua Lock
2011-01-20 16:02 ` Gary Thomas
2011-01-20 16:04 ` Koen Kooi
2011-01-20 16:34 ` Gary Thomas
2011-01-20 16:40 ` Gary Thomas
2011-01-21 14:14 ` Richard Purdie
2011-01-21 14:10 ` Richard Purdie
2011-01-21 14:25 ` Gary Thomas
2011-01-21 16:17 ` Richard Purdie [this message]
2011-01-21 20:48 ` Gary Thomas
2011-01-22 17:44 ` Gary Thomas
2011-01-28 7:42 ` Xu, Dongxiao
2011-01-28 7:49 ` Tian, Kevin
2011-02-08 18:06 ` Richard Purdie
2011-01-28 10:34 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295626657.14388.31197.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox