Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with the autobuilders: removing 1379 builds from the history?
Date: Tue, 28 May 2013 21:45:40 +0200	[thread overview]
Message-ID: <51A50964.7090503@mind.be> (raw)
In-Reply-To: <20130528091052.16da9159@skate>

On 28/05/13 09:10, Thomas Petazzoni wrote:
> This means that when you try to reproduce the build, if you take the
> Git commit id given by the autobuilder website, then you won't be
> testing with the Git commit id with which the build was made, which is
> quite annoying. This is what happened to me when trying to reproduce
> the flex problem: I have a script that, given a build SHA1, downloads
> the configuration and Git commit ID, and restarts the build with the
> exact same commit and the exact same configuration. But for those
> builds who reported an invalid Git commit ID... it cannot work, and
> therefore I wasn't reproducing the flex problem.
>
> Therefore, I am considering removing those completely bogus build
> results from the history. We are talking about removing 1379 build
> results, i.e all builds done my autobuilder between May, 14th and today.
>
> Even though it is quite annoying to lose so many results, I believe
> this is the best action we can take now.

  I would wait a couple of days before removing them. At least for the 
most recent ones, current HEAD probably still exposes the same problem, 
so in that sense the build result is still usable.

  Would it be possible to direct the URLs to a placeholder page 
explaining that the build result was removed, so existing links in commit 
messages don't die?


  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-05-28 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28  7:10 [Buildroot] Issue with the autobuilders: removing 1379 builds from the history? Thomas Petazzoni
2013-05-28  7:25 ` Yann E. MORIN
2013-05-28  7:57   ` Peter Korsgaard
2013-05-28 19:45 ` Arnout Vandecappelle [this message]
2013-05-28 19:47   ` Thomas Petazzoni
2013-05-28 19:49     ` Arnout Vandecappelle

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=51A50964.7090503@mind.be \
    --to=arnout@mind.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox