[bitbake-devel] [PATCH v5] fetch/gitsm: avoid live submodule fetching during unpack()

Matt Hoosier matt.hoosier at gmail.com
Wed Jun 6 13:36:35 UTC 2018


On Wed, Jun 6, 2018 at 5:19 AM Richard Purdie <
richard.purdie at linuxfoundation.org> wrote:

> On Fri, 2018-05-25 at 08:45 -0500, Matt Hoosier wrote:
> > Although the submodules' histories have been fetched during the
> > do_fetch() phase, the mechanics used to clone the workdir copy
> > of the repo haven't been transferring the actual .git/modules
> > directory from the repo fetched into downloads/ during the
> > fetch task.
> >
> > Fix that, and for good measure also explicitly tell Git to avoid
> > hitting the network during do_unpack() of the submodules.
> >
> > [YOCTO #12739]
> >
> > Signed-off-by: Matt Hoosier <matt.hoosier at gmail.com>
> > ---
> >  lib/bb/fetch2/gitsm.py | 84
> > +++++++++++++++++++++++++++++++++++++++++++++-----
> >  1 file changed, 76 insertions(+), 8 deletions(-)
>
> I hate to say this but we saw another failure from this :(
>
>
> https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/1099/steps/Running%20oe-selftest/logs/stdio
>
> (the second one, grep for submodule deinit)
>
> This was running on the centos 7 worker so I suspect older git versions
> don't have the options you're using.
>
> Cheers,
>
> Richard
>
>
>
Okay, I'll see what's going on with that. I'm still interested to know if
there's a listing of all the various automated regimens that are used as CI
before accepting Bitbake/Poky patches -- I don't want to keep wasting the
maintainers' time with failures that I could have uncovered independently.

Any comments on the aims and overall technique of this change? So far all
I've really gotten back are copy/pastes of automated builder failures.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20180606/a84feeef/attachment-0002.html>


More information about the bitbake-devel mailing list