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
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
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: pokybu...@fedora25.yocto.io [mailto:pokybu...@fedora25.yocto.io]
Sent: Mond
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 : 88989ae3abe98b30089e7518d3a
