All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Perez Carranza, Jose" <jose.perez.carranza@intel.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Test Cycle Report for Yocto Project master branch
Date: Thu, 16 Jun 2016 11:43:59 +0100	[thread overview]
Message-ID: <1466073839.13979.263.camel@linuxfoundation.org> (raw)
In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A01FB0CBE@fmsmsx101.amr.corp.intel.com>

Hi Jose,

Thanks for this, its useful.

On Tue, 2016-06-14 at 13:08 +0100, Perez Carranza, Jose wrote:
> -         Toaster - NameError when trying to search a table due
> Django, this one is blocking around 30% of the execution : 9749 [1]

I'm hoping this one has been fixed/merged but am not 100% sure.

> -         Build Appliance : bitbake fails to build image this one is
> blocking 50% of the  execution of the component: 9758 [2]

I know there have been some fixes here, we need to retest this to see
if we're doing better.

> -         Failed to extract rootfs by using runqemu-extract-sd: is
> blocking around 11% of the execution of ADT in 2 ditros: 9761 [3]

Unknown :(

> -         Missing smart packages: 9754 duplicated of 9717 [4]

Bill/Alejandero working on it but no patch yet.

> -         Failure with Git-Phyton 9742 duplicated of 9716 [5]

I think this has been fixed on the autobuilder in question and the
documentation is being updated so it should be resolved in those
places?

> -         distrodata class don't work with python3: 9744 [6]

Fixed.

> -         AUH: Make sure that works with python3: 9747 [7]

The class was fixed, that code isn't technically part of M1 so we have
a little more flexibility there but fixes are certainly in progress.

> -         Parse logs failed: 9520 [8]

This bug looks very confused with potentially multiple different
issues. Not sure one status :(

> -         oe-selftest is not running test cases from meta-yocto-bsp:
> [9] 9767

Its been marked as resolved fixed.

We ran an M1 build but it has several problems in addition to the above
so I'm not sure its ready for QA yet, we should discuss that. If we
decide its not ready, some targeted testing on the areas we're unsure
if things are fixed may be helpful.

Cheers,

Richard

 




  reply	other threads:[~2016-06-16 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 12:08 Test Cycle Report for Yocto Project master branch Perez Carranza, Jose
2016-06-16 10:43 ` Richard Purdie [this message]
2016-06-16 16:41   ` Richard Purdie
2016-06-16 16:49     ` Perez Carranza, Jose

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1466073839.13979.263.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jose.perez.carranza@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.