From: richard.purdie@linuxfoundation.org
To: "Jain, Sangeeta" <sangeeta.jain@intel.com>,
"'yocto@yoctoproject.org'" <yocto@yoctoproject.org>,
"Eggleton, Paul" <paul.eggleton@intel.com>,
'Michael Halstead' <mhalstead@linuxfoundation.org>,
"Erway, Tracey M" <tracey.m.erway@intel.com>,
"'sjolley.yp.pm@gmail.com'" <sjolley.yp.pm@gmail.com>,
"'openembedded-core-request@lists.openembedded.org'"
<openembedded-core-request@lists.openembedded.org>
Subject: Re: QA cycle report for 2.5.3 RC3
Date: Thu, 25 Apr 2019 10:55:32 +0100 [thread overview]
Message-ID: <bcc6fe9fbe54e3896d02932dbd7dac46f658c536.camel@linuxfoundation.org> (raw)
In-Reply-To: <015AB11D45F2C442929CB2765DAE738634DDCE9B@PGSMSX110.gar.corp.intel.com>
On Wed, 2019-04-24 at 06:28 +0000, Jain, Sangeeta wrote:
> That looks great to me.
> As a further improvement for sharing of test results, I am working to
> create a wiki page for consolidated
> test results. For 2.5.3, it can be viewed at:
> https://wiki.yoctoproject.org/wiki/WW16_-_2019-04-18_-_Full_Test_Cycle_2.5.3_RC3
The reasons for a wiki page are historical, mainly from the testopia
plugin to the wiki. I think going forward we should focus on having a
test report included in the release artefacts and that we shouldn't
need the wiki page.
> After you have added more results on AB, I will change some existing
> links on this web page with the new ones.
>
> Another thought I have is that since for any release, all data will
> be removed from public AB after few days of release,
> Should I include here a link to "yocto-testresults" git repo? It
> will make this wiki page more useful for reference in future as well.
Release data is moved from the autobuilder to the main public release
location, e.g.:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.2/testresults/
So if we put a test report as a release artefact, it moves with the
rest of the release artefacts and we're all good!
This avoids the need for any links as all the data is in one place.
Cheers,
Richard
next prev parent reply other threads:[~2019-04-25 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 4:58 QA cycle report for 2.5.3 RC3 Jain, Sangeeta
2019-04-23 14:31 ` richard.purdie
2019-04-24 6:28 ` Jain, Sangeeta
2019-04-25 9:55 ` richard.purdie [this message]
2019-04-23 14:35 ` richard.purdie
2019-04-23 15:01 ` [OE-core] " akuster808
2019-04-23 15:01 ` akuster808
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=bcc6fe9fbe54e3896d02932dbd7dac46f658c536.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-core-request@lists.openembedded.org \
--cc=paul.eggleton@intel.com \
--cc=sangeeta.jain@intel.com \
--cc=sjolley.yp.pm@gmail.com \
--cc=tracey.m.erway@intel.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.