Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-09-06
Date: Mon, 7 Sep 2020 20:48:49 +0200	[thread overview]
Message-ID: <20200907204849.7fdb07f3@windsurf.home> (raw)
In-Reply-To: <87v9gpa5sr.fsf@posteo.net>

Hello Aleksander,

On Mon, 07 Sep 2020 18:51:48 +0200
Alexander Egorenkov <egorenar-dev@posteo.net> wrote:

> >     arch     |             reason             |                                       url                                      
> > -------------+--------------------------------+---------------------------------------------------------------------------------
> >    mipsel    |       makedumpfile-1.6.7       | http://autobuild.buildroot.net/results/a8dacb1cc74e181c6b19b7fb4731899805bc47aa
> >     sh4      |       makedumpfile-1.6.7       | http://autobuild.buildroot.net/results/0e20c17bd604ee1168cc379061c120a2d8263e5f
> >   nds32le    |       makedumpfile-1.6.7       | http://autobuild.buildroot.net/results/000f622085b5b54c1b7f59d0c41ce1480c28b68e
>
> wasn't it fixed by commit
> 
> commit 34b3a071a0b038870379244a2c2264d8802e41a3
> Author: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> Date:   Sun Sep 6 10:00:28 2020 +0200
> 
>     package/makedumpfile: add BR2_PACKAGE_MAKEDUMPFILE_ARCH_SUPPORTS

All those build results were generated *before* the commit you mention.
If you take the build result URL, for example:

  http://autobuild.buildroot.net/results/a8dacb1cc74e181c6b19b7fb4731899805bc47aa

Then you can see a file called "gitid" which shows at which Buildroot
commit this build was done. In this case:
3d0c31633d170406ffd1678d56b7ca34aac0ee68, which predates when the
makedumpfile fix was committed.

The builds of our autobuilders are done 24/7, and each morning
(European time) we send an e-mail which notifies developers of the
builds that occurred during the past day (i.e between midnight and
midnight, European time). Therefore, it is possible to be notified of
build failures that have already been fixed in the mean time.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

       reply	other threads:[~2020-09-07 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <notmuch-sha1-49b8b2482171f546326fa9fe8d30bb8818be6e39>
     [not found] ` <87v9gpa5sr.fsf@posteo.net>
2020-09-07 18:48   ` Thomas Petazzoni [this message]
     [not found] <20200907071032.C7EB26064C@crulimr02.rockwellcollins.com>
2020-09-09 21:32 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-09-06 Ryan Barnett

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=20200907204849.7fdb07f3@windsurf.home \
    --to=thomas.petazzoni@bootlin.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