All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Re: [1.40][PATCH 0/10] Backport gitsm fetcher fixes
Date: Wed, 13 Mar 2019 18:19:06 -0500	[thread overview]
Message-ID: <58e2b543-10de-1c62-86d7-8ba0a09715d8@windriver.com> (raw)
In-Reply-To: <8edf457e-e537-9f9d-435a-e8acdcf2c3eb@gmail.com>

On 3/13/19 2:17 PM, akuster808 wrote:
> 
> 
> On 3/12/19 3:46 PM, Scott Murray wrote:
>> Backport Mark's git submodule fetcher fixes and a related testcase
>> change to the 1.40 branch so they can make their way into thud.  All
>> changes cherry-picked cleanly, and bitbake-selftest passes successfully.
>> Additional testing has been done with the Automotive Grade Linux (AGL)
>> build, which requires these fixes to build against poky thud.
> 
> Seeing errors on the AB for fedora, ubuntu, centos and debian hosts.
> 
> https://errors.yoctoproject.org/Errors/Details/232884/
> 
> Have not triaged it yet.

The error reported is not related to the gitsm fetcher.  It looks like this
failed in some sort of mirror test.

--Mark

> - armin
>>
>> Thanks,
>>
>> Scott
>>
>>
> 
> 



  reply	other threads:[~2019-03-13 23:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 22:46 [1.40][PATCH 0/10] Backport gitsm fetcher fixes Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 01/10] gitsm.py: Fix when a submodule is defined, but not initialized Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 02/10] gitsm.py: Add support for alternative URL formats from submodule files Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 03/10] tests/fetch.py: Add alternative gitsm test case Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 04/10] gitsm.py: Optimize code and attempt to resolve locking issue Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 05/10] gitsm.py: revise unpack Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 06/10] gitsm.py: Rework the shallow fetcher and test case Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 07/10] gitsm.py: Refactor the functions and simplify the class Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 08/10] gitsm.py: Fix relative URLs Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 09/10] gitsmy.py: Fix unpack of submodules of submodules Scott Murray
2019-03-12 22:46 ` [1.40][PATCH 10/10] gitsm: The fetcher did not process some recursive submodules properly Scott Murray
2019-03-13  4:38 ` [1.40][PATCH 0/10] Backport gitsm fetcher fixes akuster808
2019-03-13 19:17 ` akuster808
2019-03-13 23:19   ` Mark Hatle [this message]
2019-03-14 15:27   ` Scott Murray
2019-03-14 23:04     ` akuster808

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=58e2b543-10de-1c62-86d7-8ba0a09715d8@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 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.