From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] [RFC] tests/fetch.py: Add test showing recursion failure in url mapping
Date: Thu, 10 Sep 2015 18:16:04 -0500 [thread overview]
Message-ID: <55F20F34.6020404@windriver.com> (raw)
In-Reply-To: <1441922754-133875-1-git-send-email-mark.hatle@windriver.com>
After sending this, I realized there was an easy way to break the recursion.
See the patch sent after this one.
On 9/10/15 5:05 PM, Mark Hatle wrote:
> Adding this test results in a failure:
>
> RuntimeError: maximum recursion depth exceeded in cmp
>
> The mirror processing runs over and over and over on the same URL until the
> stack is exhausted. I do not have a proposed solution ot this problem.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> lib/bb/tests/fetch.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/bb/tests/fetch.py b/lib/bb/tests/fetch.py
> index 8486224..39df138 100644
> --- a/lib/bb/tests/fetch.py
> +++ b/lib/bb/tests/fetch.py
> @@ -405,7 +405,8 @@ class MirrorUriTest(FetcherTest):
> 'http://otherdownloads.yoctoproject.org/downloads/bitbake-1.0.tar.gz',
> 'http://downloads2.yoctoproject.org/downloads/bitbake-1.0.tar.gz'])
>
> - recmirrorvar = "https://.*/[^/]* http://AAAA/A/A/A/ \n"
> + recmirrorvar = "https://.*/[^/]* http://AAAA/A/A/A/ \n" \
> + "https://.*/[^/]* https://BBBB/B/B/B/ \n"
>
> def test_recursive(self):
> fetcher = bb.fetch.FetchData("https://downloads.yoctoproject.org/releases/bitbake/bitbake-1.0.tar.gz", self.d)
>
prev parent reply other threads:[~2015-09-10 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 22:05 [PATCH] [RFC] tests/fetch.py: Add test showing recursion failure in url mapping Mark Hatle
2015-09-10 23:16 ` Mark Hatle [this message]
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=55F20F34.6020404@windriver.com \
--to=mark.hatle@windriver.com \
--cc=bitbake-devel@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