Release Candidate Build for yocto-2.3.1. now available.

Release Candidate Build for yocto-2.3.1. now available.

[pokybuild]

A release candidate build for yocto-2.3.1. is now available at:


    https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d 
meta-qt4 : 88989ae3abe98b30089e7518d3adabe990c40a10 
refkit : bc70be2fdc2c9fb8fc9c7618770392bd0fafb0b9 
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee 
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f 
meta-gplv2 : 07e5dd2136a2a7cc069ad8c70bb422fa9d5b14f0 
poky : 4a39979c8d1e560fa54240e99734a651dfbaa63a 

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: git://git.yoctoproject.org/yocto-autobuilder\nEmail: pidge@toganlabs.com 

Re: Release Candidate Build for yocto-2.3.1. now available.

[Perez Carranza, Jose]

Hi 

This mail is kind of strange, artifacts are not published, there are not rc specified and afaiu we worked on QA for pyro 2.3.1 last month. 

Can anyone clarify this? 

Regards,
José


-----Original Message-----
From: pokybuild@fedora25.yocto.io [mailto:pokybuild@fedora25.yocto.io] 
Sent: Monday, August 21, 2017 1:01 PM
To: yocto@yoctoproject.org
Cc: pidge@toganlabs.com; Perez Carranza, Jose <jose.perez.carranza@intel.com>; Cruz, Libertad <libertad.cruz@intel.com>; otavio@ossystems.com.br; Zhao, Yi (Wind River) <yi.zhao@windriver.com>; Graydon, Tracy <tracy.graydon@intel.com>; Lock, Joshua G <joshua.g.lock@intel.com>
Subject: Release Candidate Build for yocto-2.3.1. now available.


A release candidate build for yocto-2.3.1. is now available at:


    https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d 
meta-qt4 : 88989ae3abe98b30089e7518d3adabe990c40a10 
refkit : bc70be2fdc2c9fb8fc9c7618770392bd0fafb0b9 
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee 
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f 
meta-gplv2 : 07e5dd2136a2a7cc069ad8c70bb422fa9d5b14f0 
poky : 4a39979c8d1e560fa54240e99734a651dfbaa63a 

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: git://git.yoctoproject.org/yocto-autobuilder\nEmail: pidge@toganlabs.com 

Re: Release Candidate Build for yocto-2.3.1. now available.

[Richard Purdie]

On Mon, 2017-08-21 at 12:03 -0700, Perez Carranza, Jose wrote:
> This mail is kind of strange, artifacts are not published, there are
> not rc specified and afaiu we worked on QA for pyro 2.3.1 last
> month. 
> 
> Can anyone clarify this? 

The eSDK artefacts in 2.3.1 were broken and its had to be rebuilt as
they were not functional. We're having some issues with the rebuilds
too :(.

Cheers,

Richard

Re: Release Candidate Build for yocto-2.3.1. now available.

[Cruz, Libertad]

Hello,

I have investigated on the test coverage on the ESDK functionality.  The testcases were created to cover the requirement mentioned in:
https://wiki.yoctoproject.org/wiki/Extensible_SDK_Test_Plan_(eSDK)#Requirements

It was not taken into account the installation or build process. The tool chain was built locally, then installed.
	echo 'SDK_EXT_TYPE = "minimal"' >> conf/local.conf
	bitbake core-image-minimal  -c populate_sdk_ext
	echo 'INHERIT += "testsdk"' >> conf/local.conf

Hence the scenario where ESDK artifacts are downloaded manually from the server where never tested. We are missing  manual scenarios to cover ESDK installation options. I have opened a bug to cover this on the next testrun https://bugzilla.yoctoproject.org/show_bug.cgi?id=11963



Best Regards
Libertad G.

-----Original Message-----
From: Purdie, Richard 
Sent: Monday, August 21, 2017 3:44 PM
To: Perez Carranza, Jose <jose.perez.carranza@intel.com>; yocto@yoctoproject.org
Cc: pidge@toganlabs.com; Cruz, Libertad <libertad.cruz@intel.com>; otavio@ossystems.com.br; Zhao, Yi (Wind River) <yi.zhao@windriver.com>; Graydon, Tracy <tracy.graydon@intel.com>; Lock, Joshua G <joshua.g.lock@intel.com>; Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: Release Candidate Build for yocto-2.3.1. now available.

On Mon, 2017-08-21 at 12:03 -0700, Perez Carranza, Jose wrote:
> This mail is kind of strange, artifacts are not published, there are 
> not rc specified and afaiu we worked on QA for pyro 2.3.1 last month.
> 
> Can anyone clarify this?

The eSDK artefacts in 2.3.1 were broken and its had to be rebuilt as they were not functional. We're having some issues with the rebuilds too :(.

Cheers,

Richard