From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Long delays with latest bitbake (was: [PATCH 1/7] insane.bbclass: in file-rdeps do not look into RDEPENDS recursively)
Date: Thu, 15 Aug 2019 23:44:13 +0100 [thread overview]
Message-ID: <9e75c7c4fa442cfc62a9a171e573a6aedf77ae27.camel@linuxfoundation.org> (raw)
In-Reply-To: <21c7f2ef52a0776dbdc9ac948d3e964d0fd937af.camel@linuxfoundation.org>
On Thu, 2019-08-15 at 14:56 +0100, richard.purdie@linuxfoundation.org
wrote:
> On Thu, 2019-08-15 at 14:56 +0200, Alexander Kanavin wrote:
> What is really odd is this on both traces:
>
> 524436 405.102 0.001 405.266 0.001
> /home/alexander/development/poky/bitbake/lib/bb/cooker.py:264(notific
> ations)
>
> What that means is that cooker recieved notification of 524436 file
> changes whilst it was parsing/preparing runqueue.
>
> I would be very interested to understand which files its being
> notified
> of changes to as I suspect there is something that shouldn't be
> there.
This is a bit of a false lead. At least locally I found them to be
profiles of the individual tasks being written out which is only
triggered on profiled builds.
We should write those files to a different directory to avoid this
confusion of the profiles...
Cheers,
Richard
next prev parent reply other threads:[~2019-08-15 22:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 20:26 Long delays with latest bitbake (was: [PATCH 1/7] insane.bbclass: in file-rdeps do not look into RDEPENDS recursively) Peter Kjellerstedt
2019-08-13 9:04 ` Richard Purdie
2019-08-13 13:20 ` Alexander Kanavin
2019-08-13 19:18 ` Richard Purdie
2019-08-14 4:06 ` Khem Raj
2019-08-14 11:25 ` Alexander Kanavin
2019-08-14 11:36 ` richard.purdie
2019-08-14 12:08 ` Alexander Kanavin
2019-08-14 12:43 ` Alexander Kanavin
2019-08-14 12:50 ` Mikko.Rapeli
2019-08-14 12:55 ` richard.purdie
2019-08-14 14:57 ` Peter Kjellerstedt
2019-08-14 15:19 ` Khem Raj
2019-08-14 20:27 ` Alexander Kanavin
2019-08-14 21:25 ` richard.purdie
2019-08-15 12:56 ` Alexander Kanavin
2019-08-15 13:56 ` richard.purdie
2019-08-15 22:44 ` Richard Purdie [this message]
2019-08-15 15:05 ` Martin Jansa
2019-08-16 10:24 ` Martin Jansa
2019-08-16 15:00 ` Martin Jansa
2019-08-16 15:54 ` richard.purdie
2019-08-16 17:22 ` Martin Jansa
2019-08-19 21:23 ` Martin Jansa
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=9e75c7c4fa442cfc62a9a171e573a6aedf77ae27.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.