From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: long (never ending?) do_install for adwaita-icon-theme
Date: Wed, 23 Aug 2017 15:48:06 +0300 [thread overview]
Message-ID: <9f0302e4-4320-b985-e0b8-ebf3f7422aad@linux.intel.com> (raw)
In-Reply-To: <e165f760-1c1e-1a5f-2fba-f8c293a16278@intel.com>
On 08/22/2017 09:46 PM, Trevor Woerner wrote:
>> Do you have any kind of logs for when it happens?
>
>
> Unfortunately not, I'll try to keep some the next time it happens.
>
> But I have a suspicion it might be related to a build failure. Earlier
> today I was doing a build which failed in a recipe that wasn't
> adwaita-icon-theme, nor related to it. When I checked on my build
> later I could see the tail of the error message from the failed
> recipe, but the overall build was still waiting for
> adwaita-icon-theme's do_install to finish (hours after the failure).
>
> Maybe adwaita-icon-theme's do_install would have succeeded if
> everything had gone well? Maybe to reproduce, it might be necessary to
> time it such that another recipe fails while adwaita-icon-theme is
> building?
We can certainly revert my patch that speeds up the do_install(), but I
would prefer not to do it blindly: it's much better to first firmly
establish that the patch is indeed the reason for the never ending
do_install (I can't imagine why, but it certainly could be). So please
do try to get some logs, or a stable way to reproduce.
Alex
next prev parent reply other threads:[~2017-08-23 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 17:32 long (never ending?) do_install for adwaita-icon-theme Trevor Woerner
2017-08-22 17:40 ` Richard Purdie
2017-08-22 18:01 ` Alexander Kanavin
2017-08-22 18:46 ` Trevor Woerner
[not found] ` <e165f760-1c1e-1a5f-2fba-f8c293a16278@intel.com>
2017-08-23 12:48 ` Alexander Kanavin [this message]
2017-08-27 16:01 ` Richard Purdie
2017-08-27 16:07 ` Richard Purdie
2017-08-28 10:38 ` Alexander Kanavin
2017-08-28 14:43 ` Richard Purdie
2017-08-28 15:14 ` Alexander Kanavin
2017-08-28 15:27 ` Alexander Kanavin
2017-08-28 16:22 ` Richard Purdie
2017-08-28 17:53 ` Khem Raj
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=9f0302e4-4320-b985-e0b8-ebf3f7422aad@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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