All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: richard.purdie@linuxfoundation.org, "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>,
	"otavio@ossystems.com.br" <otavio@ossystems.com.br>,
	"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>
Subject: Re: QA notification for completed autobuilder build (yocto-2.6.2.rc3)
Date: Fri, 5 Apr 2019 03:46:04 +0530	[thread overview]
Message-ID: <5f279a38-ec01-21b5-e683-a9bc3caa8235@gmail.com> (raw)
In-Reply-To: <dd9d4804a3b42d84b0dcac0d35e3d1a1a4f0146a.camel@linuxfoundation.org>



On 4/5/19 3:25 AM, richard.purdie@linuxfoundation.org wrote:
> On Thu, 2019-04-04 at 02:19 +0000, Jain, Sangeeta wrote:
>> Also, I don't see any ptest results for 2.6.2.rc3 on public
>> autobuilder. Do you have any plans to run them and share the results
>> on autobuilder?
> These were run separately but will run as part of any new stable
> release builds. The results are here:
>
> https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/
> https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/
>
> (for 2.6.2 and 2.5.4)
>
> I'll merge these into the main release output in due course.
Did I miss something in order to create:
https://autobuilder.yocto.io/pub/non-release/20190326-8/testresults/testresult-report.txt

- Armin
>
> Cheers,
>
> Richard
>



  reply	other threads:[~2019-04-04 22:16 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
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 [this message]
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=5f279a38-ec01-21b5-e683-a9bc3caa8235@gmail.com \
    --to=akuster808@gmail.com \
    --cc=aaron.chun.yew.chan@intel.com \
    --cc=otavio@ossystems.com.br \
    --cc=pokybuild@ubuntu1604-ty-1.yocto.io \
    --cc=richard.purdie@linuxfoundation.org \
    --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.