All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: "Jain, Sangeeta" <sangeeta.jain@intel.com>,
	Poky Build User <pokybuild@ubuntu1604-ty-1.yocto.io>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>,
	 Yi Zhao <yi.zhao@windriver.com>
Cc: "akuster808@gmail.com" <akuster808@gmail.com>,
	"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>,
	"otavio@ossystems.com.br" <otavio@ossystems.com.br>
Subject: Re: QA notification for completed autobuilder build (yocto-2.6.2.rc3)
Date: Wed, 03 Apr 2019 10:20:01 +0100	[thread overview]
Message-ID: <8322586b16a5bda01770480f7096837c13d26f6b.camel@linuxfoundation.org> (raw)
In-Reply-To: <015AB11D45F2C442929CB2765DAE738634DB02DA@PGSMSX110.gar.corp.intel.com>

Hi,

This is good information and helps a lot, thanks! I had a question
below.

On Wed, 2019-04-03 at 08:06 +0000, Jain, Sangeeta wrote:
> Intel and WR YP QA is now working on QA execution for YP build 2.6.2
> RC3. We are planning to execute following tests for this cycle:
> 
> OEQA-Manual tests for following modules:
> 1.	SDK
> 2.	Eclipse-plugin
> 3.	Kernel
> 4.	Toaster
> 5.	Bitbake (oe-core)
> 6.	Build-appliance
> 7.	Crops
> 8.	Compliance-test
> 9.	Bsp-hw
> 10.	Bsp-qemu
> 
> Runtime auto test for following platforms:
> 
> 1.	MinnowTurbo 32bit
> 2.	MinnowTurbot 64 bit
> 3.	NUC 7
> 4.	NUC 6
> 5.	Edgerouter
> 6.	MPC8315e-rdb
> 7.	Beaglebone
> 8.	Qemuarm
> 9.	Qemuarm-64
> 10.	Qemuppc
> 11.	Qemumips
> 12.	Qemumips64

I'm wondering if there is any difference between items 8-12 here and
the runtime testing we run on the public autobuilder? Is there some
testing we're missing on the public autobuilder?

Cheers,

Richard




  reply	other threads:[~2019-04-03  9:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28  3:30 QA notification for completed autobuilder build (yocto-2.6.2.rc3) Poky Build User
2019-04-03  8:06 ` Jain, Sangeeta
2019-04-03  9:20   ` richard.purdie [this message]
2019-04-04  2:19     ` Jain, Sangeeta
2019-04-04  5:39       ` Yeoh, Ee Peng
2019-04-04 21:55       ` richard.purdie
2019-04-04 22:16         ` akuster808
2019-04-04 22:23           ` richard.purdie
2019-04-05  0:58             ` Tim Orling
2019-04-05  3:39               ` akuster
2019-04-05  5:03                 ` Tim Orling
2019-04-05  6:47               ` richard.purdie
2019-04-03  9:50   ` akuster808
2019-04-03 10:24     ` Yeoh, Ee Peng

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=8322586b16a5bda01770480f7096837c13d26f6b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=aaron.chun.yew.chan@intel.com \
    --cc=akuster808@gmail.com \
    --cc=otavio@ossystems.com.br \
    --cc=pokybuild@ubuntu1604-ty-1.yocto.io \
    --cc=sangeeta.jain@intel.com \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=yi.zhao@windriver.com \
    --cc=yocto@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.