krogoth 2.1.2 status

krogoth 2.1.2 status

[Richard Purdie]

I ran a krogoth 2.1.2 build. It did have some issues:

* one runtime sanity test had a timeout issue
* some urls are stale (perpetual problem)
* musl runtime testing fails (never tested on krogoth previously)
* no-x11 runtime testing had a failure (never tested on krogoth
previously)

I suspect we can call this good enough to put into QA but there were
enough 'failures' I wanted to send this out in case someone objects.

Part of the problem here is we apply our current autobuilder test setup
to the older releases as well. I'm aware there may be better ways to do
this but I don't know anyone with time to work on that, we have other
more pressing problems.

Cheers,

Richard

Re: krogoth 2.1.2 status

[Joshua Lock]

On Wed, 2016-11-09 at 12:30 +0000, Richard Purdie wrote:
> I ran a krogoth 2.1.2 build. It did have some issues:
> 
> * one runtime sanity test had a timeout issue
> * some urls are stale (perpetual problem)
> * musl runtime testing fails (never tested on krogoth previously)
> * no-x11 runtime testing had a failure (never tested on krogoth
> previously)

We can update the autobuilder not to run these tests for krogoth.
I've filed a bug for musl:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10634

for no-x11 there's a single failure, it might be worthwhile backporting
fixes to make that work?

Regards,

Joshua

Re: krogoth 2.1.2 status

[akuster808]

On 11/09/2016 04:30 AM, Richard Purdie wrote:
> I ran a krogoth 2.1.2 build. It did have some issues:
>
> * one runtime sanity test had a timeout issue
> * some urls are stale (perpetual problem)
> * musl runtime testing fails (never tested on krogoth previously)
> * no-x11 runtime testing had a failure (never tested on krogoth
> previously)
Can we get those issues bugged ( if not done so already) so we can make 
decisions on what to do with each.
>
> I suspect we can call this good enough to put into QA but there were
> enough 'failures' I wanted to send this out in case someone objects.
>
> Part of the problem here is we apply our current autobuilder test setup
> to the older releases as well. I'm aware there may be better ways to do
> this but I don't know anyone with time to work on that, we have other
> more pressing problems.
I suspect Jethro will have similar or worse issues.

- Armin
>
> Cheers,
>
> Richard
>

Re: krogoth 2.1.2 status

[Perez Carranza, Jose]

Hi 

Based on below comments we will start the QA cycle for 2.1.2, we will start tomorrow once the QA cycle for meta-intel is finished. 

Regards,
José


-----Original Message-----
From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org] 
Sent: Wednesday, November 9, 2016 6:30 AM
To: openembedded-core <openembedded-core@lists.openembedded.org>; Armin Kuster <akuster808@gmail.com>
Cc: Perez Carranza, Jose <jose.perez.carranza@intel.com>; Jolley, Stephen K <stephen.k.jolley@intel.com>; Delgado, Sonia <sonia.delgado@intel.com>
Subject: krogoth 2.1.2 status

I ran a krogoth 2.1.2 build. It did have some issues:

* one runtime sanity test had a timeout issue
* some urls are stale (perpetual problem)
* musl runtime testing fails (never tested on krogoth previously)
* no-x11 runtime testing had a failure (never tested on krogoth
previously)

I suspect we can call this good enough to put into QA but there were enough 'failures' I wanted to send this out in case someone objects.

Part of the problem here is we apply our current autobuilder test setup to the older releases as well. I'm aware there may be better ways to do this but I don't know anyone with time to work on that, we have other more pressing problems.

Cheers,

Richard