From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autobuild-run: remove only tarballs from download dir
Date: Sun, 15 Apr 2018 21:49:15 +0200 [thread overview]
Message-ID: <20180415194915.GE21958@scaer> (raw)
In-Reply-To: <20180415214257.1e90704a@windsurf.numericable.fr>
Thomas, Ricardo, All,
On 2018-04-15 21:42 +0200, Thomas Petazzoni spake thusly:
> On Fri, 13 Apr 2018 10:34:31 -0300, Ricardo Martincoski wrote:
>
> > diff --git a/scripts/autobuild-run b/scripts/autobuild-run
> > index 33d0ae9..6a01151 100755
> > --- a/scripts/autobuild-run
> > +++ b/scripts/autobuild-run
> > @@ -291,6 +291,9 @@ def prepare_build(**kwargs):
> > # recursively find files under root
> > def find_files(root):
> > for r, d, f in os.walk(root):
> > + if '.git' in d:
> > + d[:] = list()
> > + continue
>
> Just to check how this is supposed to work. We have this:
>
> dl/<package>/git/.git
>
> Correct ?
>
> So you're idea is that when we are inside dl/<package>/git/, one of the
> sub-directories is .git, and therefore we shouldn't remove anything in
> dl/<package>/git/ ?
>
> My concern is that I'm not sure if what you've done prevents from
> removing files inside dl/<package>/git or only inside
> dl/<package>/git/.git. I would find it more to do something like:
>
> if "git" in d:
> d.remove("git")
>
> but perhaps you haven't done this for some good reason ?
>
> Another concern is how to fix those autobuilders that have already
> removed some random files from their cached Git repositories? Should we
> ask the people who run those autobuilders to entirely wipe the download
> folders of their autobuilder instances ? Or do we have a smart (but
> simple) thing to do to avoid this ?
For this last part, we've already discused this with Ricardo in another
thread: we run git-fsck, and if there is an error, we ditch the git tree
and clone from scratch.
See the current work I have to further robustify (does that even exist?)
the git backend:
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/git-robust
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-04-15 19:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 13:34 [Buildroot] [PATCH] autobuild-run: remove only tarballs from download dir Ricardo Martincoski
2018-04-15 19:42 ` Thomas Petazzoni
2018-04-15 19:49 ` Yann E. MORIN [this message]
2018-04-15 20:02 ` Thomas Petazzoni
2018-04-15 20:10 ` Yann E. MORIN
2018-04-15 20:38 ` Thomas Petazzoni
2018-04-15 20:59 ` Yann E. MORIN
2018-04-15 23:18 ` Ricardo Martincoski
2018-04-15 22:23 ` Ricardo Martincoski
2018-04-16 9:01 ` Yann E. MORIN
2018-04-16 16:05 ` Thomas Petazzoni
2018-04-16 16:09 ` Thomas Petazzoni
2018-04-17 4:38 ` Ricardo Martincoski
2018-04-17 7:12 ` [Buildroot] [PATCH v2] " Ricardo Martincoski
2018-04-19 21:39 ` Thomas Petazzoni
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=20180415194915.GE21958@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.