Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Changqing Li" <changqing.li@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Cc: "MacLeod, Randy (Wind River)" <randy.macleod@windriver.com>
Subject: Re: [OE-core] [PATCH] libpcre: fix occasionally do_package_write_rpm error
Date: Wed, 2 Sep 2020 10:36:53 +0800	[thread overview]
Message-ID: <61b74cbe-c228-c206-9155-0e3a0d866e4f@windriver.com> (raw)
In-Reply-To: <389322665bc193ed7bace452717e02dd80aa675d.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]


On 9/1/20 7:08 PM, Richard Purdie wrote:
> On Fri, 2020-08-28 at 14:14 +0800, Changqing Li wrote:
>> From: Changqing Li <changqing.li@windriver.com>
>>
>> Error info:
>> ERROR: libpcre-8.44-r0 do_package_write_rpm: Failure expanding
>> variable
>> SUMMARY_libpcrecpp, expression was ${SUMMARY} - C++ wrapper functions
>> which triggered exception RecursionError: maximum recursion depth
>> exceeded while calling a Python object
>>
>> this error is hard to reproduce, only met one time. Seems expand
>> SUMMARY with reference to SUMMARY cause a dead loop.
>>
>> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> What is worrying me is why we can't reproduce this. It should fail or
> not fail, why do we only sometimes see this?
>
> I'd like to understand the cause as it sounds like a determinism
> problem somewhere.
>
> Is there a sequence we can reproduce it with?

Unfortunately no, we also hard to reproduce this, only met one time on 
08 Jul when build a wrlinux image.

And don't see it for about 2 months.

>
> Cheers,
>
> Richard
>
>
> 

[-- Attachment #2: Type: text/html, Size: 3006 bytes --]

  reply	other threads:[~2020-09-02  2:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28  6:14 [PATCH] libpcre: fix occasionally do_package_write_rpm error Changqing Li
2020-09-01 11:08 ` [OE-core] " Richard Purdie
2020-09-02  2:36   ` Changqing Li [this message]
2020-09-02  7:17     ` 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=61b74cbe-c228-c206-9155-0e3a0d866e4f@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.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