Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-01-04
Date: Fri, 5 Jan 2018 09:59:38 +0100	[thread overview]
Message-ID: <20180105095938.39a18748@windsurf.lan> (raw)
In-Reply-To: <20180105084309.GB8058@airbook.vandijck-laurijssen.be>

Hello,

On Fri, 5 Jan 2018 09:43:09 +0100, Kurt Van Dijck wrote:

> > Results for the 'master' branch
> > ===============================
> > 
> > Build failures related to your packages:
> > 
> >       xtensa |             nilfs-utils-v2.2.7 | http://autobuild.buildroot.net/results/a9fe41ed428d26ef5500cec9f762c0bae3eebd39  
> 
> I just ran this on my local branch, including the patches I sent
> yesterday (and are still pending), and that went ok, so I propose
> to wait and see until those 2 patches are accepted/denied.
> 
> Just a question.
> I don't understand why xtensa fails today and not yesterday ...
> Is there a random toolchain selection everyday for each package to save
> buildserver resources?

The autobuilders only do random testing. Essentially, what they do is:

 - Pick a random architecture/toolchain configuration among the one
   available in support/config-fragments/autobuild/

 - Run "make randpackageconfig" to generate on top of the
   architecture/toolchain configuration a random selection of packages.

 - Build

So the results every day are different, since it's completely random
what testing is being done. This allows us to test a very wide variety
of package/toolchain/architecture combinations, since doing an
exhaustive testing is simply impossible when you have thousands of
Config.in options.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

       reply	other threads:[~2018-01-05  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180105070004.41340207B4@mail.free-electrons.com>
     [not found] ` <20180105084309.GB8058@airbook.vandijck-laurijssen.be>
2018-01-05  8:59   ` Thomas Petazzoni [this message]
2018-01-05  9:24     ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-01-04 Kurt Van Dijck

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=20180105095938.39a18748@windsurf.lan \
    --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