From: Richard Purdie <richard.purdie@intel.com>
To: "Serban, Laurentiu" <laurentiu.serban@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Wold, Saul" <saul.wold@intel.com>
Subject: Re: 1.3 M3 Full Pass test results
Date: Fri, 24 Aug 2012 11:21:51 +0100 [thread overview]
Message-ID: <1345803711.14369.69.camel@ted> (raw)
In-Reply-To: <E16513A01CAAFF40B65178C63CE45EEC1917553B@IRSMSX102.ger.corp.intel.com>
On Thu, 2012-08-23 at 20:13 +0100, Serban, Laurentiu wrote:
> Here are the results for the full pas tests on 1.3 M3 RC2. The commit
> used for testing is 8b8748c8f963900b83dc0fdd7757556f917fe4fd.
>
> Some details about the encountered issues below:
>
> BSP – Sudoku-savant project build issue (2878)
>
> ADT – the relocatable sdk issue (2980) causes 13 test cases to be on
> faile/blocked state
I thought it worked as long as you didn't have to relocate it so no
tests should have been blocked, we just have the relocation issue?
> , also the Clutter C template issue is unsolved (2577)
>
> Core Build System – x32 is still an issue (2888), cleaning sstate
> issue is still not solved (2897), incremental RPM image generation
> (2969), source archiving (2619), the kvm issue was reproduced by
> another colleague (2790) Yocto BSP creation via JSON (2693) or for
> qemu (2991) fails, multilib issue (2918 – this requires a little more
> investigation from QA),
>
> HOB - all seems ok for RC2
>
> Self-hosted-image - cannot start on Virtual Box (X issue), it is very
> slow on qemu and it has a m4 package build (3005) issue on VMWare. If
> the self-hosted-image is used on machine with internet connectivity
> via proxy there will be an initial sanity check failure, but this is
> not a blocking issue.
>
> A mention for the performance testing: on a Ubbuntu 12.04 i7 machine
> using 8 threads the build time was 83 minutes (with prior fetching).
How does this compare with our other performance numbers. From what I
remember, we used to hover around the 105-115 minute mark. Did we have
some significant speed gains or is this just an artefact of changing the
test machine?
Cheers,
Richard
next prev parent reply other threads:[~2012-08-24 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 19:13 1.3 M3 Full Pass test results Serban, Laurentiu
2012-08-24 10:21 ` Richard Purdie [this message]
2012-08-24 13:33 ` Serban, Laurentiu
2012-08-27 17:49 ` Liu, Song
2012-08-27 18:14 ` Serban, Laurentiu
2012-08-28 0:47 ` Xu, Jiajun
2012-08-27 16:27 ` Saxena, Rahul
2012-08-27 18:17 ` Serban, Laurentiu
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=1345803711.14369.69.camel@ted \
--to=richard.purdie@intel.com \
--cc=laurentiu.serban@intel.com \
--cc=saul.wold@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.