All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Hoosier <matt.hoosier@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v5] fetch/gitsm: avoid live submodule fetching during unpack()
Date: Wed, 6 Jun 2018 12:00:40 -0500	[thread overview]
Message-ID: <CAJgxT39m+ex8F+mjaq5+zzxps7DaPO=iUu=1PO=U3SW-NWp5_Q@mail.gmail.com> (raw)
In-Reply-To: <f6d6f5fa735580808180883de3eed143c10d6002.camel@linuxfoundation.org>

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

On Wed, Jun 6, 2018 at 9:03 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Wed, 2018-06-06 at 08:36 -0500, Matt Hoosier wrote:
> > Okay, I'll see what's going on with that.


I've posted an updated copy at
http://lists.openembedded.org/pipermail/bitbake-devel/2018-June/009365.html
that address the usage of the submodule commands that were too new for
CentOS. Fortunately, their usage was basically unnecessary -- I just
deleted them outright.


> 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.
>
> The test matrix is basically encoded into:
>
>
> http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder-helper/tree/config.json
>
> run across the various autobuilder workers on https://autobuilder.yocto
> .io/buildslaves, i.e. centos7, debian8, debian9, fedora26, fedora27,
> opensuse423, opensuse tumbleweed, ubuntu 1604 and ubuntu 1704
>
> I'm not sure its reasonable to expect everyone to test across all those
> combinations!
>

Okay, I agree. :)

I think I've managed to test at the new and old ends of each of the major
distro families there, so I'll be content let the autobuilder sniff out any
more corner cases.


>
> > 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.
>
> I strongly believe we should only have network access in do_fetch and
> that our source mirroring should be functional and I therefore very
> much support what the patch is doing and appreciate this getting fixed.
>
> Sorry for the terse nature of the replies, we're just seeing a lot of
> patches which are breaking the regression tests and its hard to root
> cause them back to the underlying patches and help people debug them.
>
> I do appreciate the help in getting this issue fixed as it will be a
> good improvement to the fetcher.
>
> Cheers,
>
> Richard
>

Sounds great; thanks, Richard.

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

  reply	other threads:[~2018-06-06 17:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 13:45 [PATCH v5] fetch/gitsm: avoid live submodule fetching during unpack() Matt Hoosier
2018-06-01 14:02 ` Matt Hoosier
2018-06-01 14:20   ` Alexander Kanavin
2018-06-06 10:19 ` Richard Purdie
2018-06-06 13:36   ` Matt Hoosier
2018-06-06 14:02     ` Richard Purdie
2018-06-06 17:00       ` Matt Hoosier [this message]
2018-06-07 13:47         ` Matt Hoosier
2018-06-08 10:20           ` Richard Purdie
2018-06-08 12:36             ` Matt Hoosier
2018-06-08 13:17               ` Joshua Watt
2018-06-08 13:27                 ` Matt Hoosier

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='CAJgxT39m+ex8F+mjaq5+zzxps7DaPO=iUu=1PO=U3SW-NWp5_Q@mail.gmail.com' \
    --to=matt.hoosier@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --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 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.