[yocto] 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 at intel.com>; yocto at yoctoproject.org
Cc: pidge at toganlabs.com; Cruz, Libertad <libertad.cruz at intel.com>; otavio at ossystems.com.br; Zhao, Yi (Wind River) <yi.zhao at windriver.com>; Graydon, Tracy <tracy.graydon at intel.com>; Lock, Joshua G <joshua.g.lock at intel.com>; Michael Halstead <mhalstead at 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