All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "McClintock Matthew-B29882" <B29882@freescale.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 1/1] conf/distro/poky.conf: set SANITY_TESTED_DISTROS
Date: Tue, 27 Sep 2011 17:40:05 +0100	[thread overview]
Message-ID: <201109271740.05725.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <CAEsOVNd=Ns1EfSBewKMoiMhDz9DvX9h-ULrJQkLa+h08XEfKJw@mail.gmail.com>

On Tuesday 27 September 2011 17:19:50 you wrote:
> The other question is what MACHINE's we build for - it should be
> fairly comprehensive to just test for one, but it's hardly adequate...
> I'd assume x86, arm, ppc, mips all need to be build tested and boot
> tested?

I'm not sure we need to go that far. We do run such comprehensive tests for a 
small list of common distros as part of the core testing done by the Yocto QA 
team. However, whilst it's entirely possible that a host distribution might 
cause failures with one MACHINE / TARGET_ARCH and not another, in practice I 
would expect that if a build of a fairly comprehensive image (such as core-
image-sato) for one machine is able to complete successfully and run within 
QEMU then that should be a good indicator that the host distro is suitable. 
Additionally, if builds are being run on that system on a regular basis (e.g. 
the autobuilders, or a developer's main machine) then that would of course 
increase the level of confidence in that distribution.

Naturally, resources allowing we would like to have full batches of tests run 
on more distributions, but I don't think it's practical to commit to testing 
every distro.

Jiajun might have some other opinions/experience here, Jiajun...?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2011-09-27 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 13:24 [PATCH 0/1] Set tested distros list Paul Eggleton
2011-09-27 13:24 ` [PATCH 1/1] conf/distro/poky.conf: set SANITY_TESTED_DISTROS Paul Eggleton
     [not found]   ` <CAEsOVNc3BQLKkHHmvRE6oDe6k8CA_3Lybgqh8XmvLyNA+xhQ2A@mail.gmail.com>
2011-09-27 16:10     ` Paul Eggleton
     [not found]       ` <CAEsOVNd=Ns1EfSBewKMoiMhDz9DvX9h-ULrJQkLa+h08XEfKJw@mail.gmail.com>
2011-09-27 16:40         ` Paul Eggleton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-17 23:46 [PATCH 0/1] [1.2] Enable untested distribution warning Paul Eggleton
2012-04-17 23:46 ` [PATCH 1/1] conf/distro/poky.conf: set SANITY_TESTED_DISTROS Paul Eggleton
2012-04-18  7:00   ` Saul Wold
2012-04-18 10:03 [PATCH 0/1] Enable untested distribution warning v2 Paul Eggleton
2012-04-18 10:03 ` [PATCH 1/1] conf/distro/poky.conf: set SANITY_TESTED_DISTROS Paul Eggleton

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=201109271740.05725.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=B29882@freescale.com \
    --cc=poky@yoctoproject.org \
    /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.