From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder reporting old build issues
Date: Sun, 16 Jul 2017 10:20:02 +0200 [thread overview]
Message-ID: <20170716102002.6d570790@windsurf> (raw)
In-Reply-To: <20170715100105.108fb7ab@windsurf>
Hello Matt,
On Sat, 15 Jul 2017 10:01:05 +0200, Thomas Petazzoni wrote:
> Is there something special going on with your autobuilder setup?
> Indeed, it very often reports build results that are based on Buildroot
> versions that are a few days old, as if you're not testing the latest
> Buildroot.
>
> For example, if you look at the attached screenshot, all autobuilder
> instances reported results based on Buildroot 05827480 (the strace
> commit I made yesterday evening), except your autobuilder results,
> which were based on 704db158 (a commit made on July 10, i.e 4-5 days
> ago).
Since your autobuilder is still reporting build results that date back
from commit 704db158, I've disabled your account so that build results
from your autobuilder are no longer accepted.
Let me know when the problem is fixed, so that I can re-enable your
account.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-16 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 8:01 [Buildroot] Autobuilder reporting old build issues Thomas Petazzoni
2017-07-15 8:04 ` Thomas Petazzoni
2017-07-16 8:20 ` Thomas Petazzoni [this message]
2017-07-17 11:18 ` Matthew Weber
2017-07-17 11:25 ` Thomas Petazzoni
2017-07-17 12:00 ` Matthew Weber
2017-07-17 12:09 ` Thomas Petazzoni
2017-07-17 13:20 ` Matthew Weber
2017-07-17 13:35 ` 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=20170716102002.6d570790@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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