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

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

Can we get those issues bugged ( if not done so already) so we can make decisions on what to do with each.

I suspect Jethro will have similar or worse issues.

- Armin

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:[email protected]]
Sent: Wednesday, November 9, 2016 6:30 AM
To: openembedded-core <[email protected]>; Armin Kuster <[email protected]>
Cc: Perez Carranza, Jose <[email protected]>; Jolley, Stephen K <[email protected]>; Delgado, Sonia <[email protected]>
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