We used to get 115m and 127m for 1.3 M1 and M2 on our test machine.
> Hello guys,
>
> I am sorry I did not notice the last line in the e-mail.
>
> When we ran the performance testing we pre-downloaded all the sources,
> because last week had a lot of connectivity issues. I mentioned in the
> e-m
Hi all,
This is the weekly bug trend for WW26. WDD number and Open Bug number
keep flat with WW25, as 1097 and 224. Bug status of WW26 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailin
Hi all,
This is the weekly bug trend for WW25. WDD number and Open Bug number
keep flat with WW24, as 1101 and 225. Bug status of WW25 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailin
Hi all,
This is the weekly bug trend for WW24. WDD number and Open Bug number
keep flat with WW23, as 1098 and 224. Bug status of WW24 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailing
Hi all,
This is the weekly bug trend for WW23. The new submitted vs. fixed bug
number is 39 vs. 25. WDD number and Open Bug number increased a lot, as 1103
and 222. Bug status of WW23 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
Hi Beth,
Will we have a new meta-intel build or we should use the old builds(20120605)
for BSP testing?
> The weekly build of 1.3_M4 Week 4 will soon be available at:
>
> http://autobuilder.yoctoproject.org/pub/nightly/20120606-1
>
> Some minor issues with the buildhistory sync step have been i
Hi all,
This is the weekly bug trend for WW21. The new submitted vs. fixed bug
number is 31 vs. 23. WDD number and Open Bug number increased a lot, as 993 and
202. Bug status of WW21 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
This is the weekly bug trend for WW20. The new submitted vs. fixed bug
number is 23 vs. 16. WDD number and Open Bug number increased a little, as 932
and 191. Bug status of WW20 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
This is the weekly bug trend for WW19. The new submitted vs. fixed bug
number is 24 vs. 36. WDD number and Open Bug number decreased a little, as 878
and 181. Bug status of WW19 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
_
Hi all,
This is the weekly bug trend for WW18. Yocto 1.2 was released last
week. The new submitted vs. fixed bug number is 51 vs. 35. WDD number and Open
Bug number increased a lot, as 893 and 184. Bug status of WW18 could be found
on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Hi all,
This is the weekly bug trend for WW16. The new submitted vs. fixed bug
number is 58 vs. 43. WDD number and Open Bug number increased a lot, as 834 and
171. Bug status of WW16 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
This is the weekly bug trend for WW15. The new submitted vs. fixed bug
number is 40 vs. 73. A lot of bugs are fixed by developers' hard working. WDD
number and Open Bug number are 759 and 155. Bug status of WW15 could be found
on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend
Hi all,
This is the weekly bug trend for WW14. The new submitted vs. fixed bug
number is 42 vs. 32. By comparing with WW13, open bug number for "Critical",
"Major" and "Normal" increased a lot. WDD number and Open Bug number are 955
and 187. Bug status of WW14 could be found on
https://
Hi all,
This is the weekly bug trend for WW13. The new submitted vs. fixed bug
number is 45 vs. 66. By comparing with WW12, open bug number for "Major",
"Normal" increased a lot. WDD number and Open Bug number are 866 and 174. Bug
status of WW13 could be found on
https://wiki.yoctoproje
Hi all,
This is the weekly bug trend for WW12. The new submitted vs. fixed bug
number is 34 vs. 42. 9 of fixed bugs are enhancement. By comparing with WW11,
there are 5 more major bugs in WW12, which causes WDD number increase with
decreased open bug number. Janitors bugs are included in
> Hi Jiajun,
>
> On Mon, 2012-03-19 at 08:49 +0000, Xu, Jiajun wrote:
>> The overall open bug trend increased a lot in last week. The new
>> submitted vs. fixed bug number is 64 vs. 52. Some fixed bugs are
>> enhancement bug, which are not calculated into WDD data.
Hi all,
The overall open bug trend increased a lot in last week. The new
submitted vs. fixed bug number is 64 vs. 52. Some fixed bugs are enhancement
bug, which are not calculated into WDD data. WDD number and Open Bug number are
938 and 188. Bug status of WW11 could be found on
https:/
>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>> boun...@yoctoproject.org] On Behalf Of Xu, Jiajun
>> Sent: Wednesday, March 14, 2012 7:09 AM
>> To: yocto@yoctoproject.org
>> Subject: [yocto] Yocto weekly bug trend charts -- WW10
>>
>> Hi all,
&g
Hi all,
The overall open bug trend increased a lot in last week. WDD number and
Open Bug number are 886 and 173. Due to the bugzilla upgrade, some functions do
not work, which make QA bug statistic a little late. Bug status of WW10 could
be found on https://wiki.yoctoproject.org/wiki/Yoc
Hi all,
The overall open bug trend increased a lot during last 2 weeks. WDD
number and Open Bug number are 819 and 164. QA began 1.2 M3 RC1 testing last
week. Bug status of WW09 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
The overall open bug trend increased a little last week. WDD number and
Open Bug number are 745 and 150. Bug status of WW07 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailing li
Hi all,
The overall open bug trend keep flat during last several weeks. WDD
number and Open Bug number are 718 and 145. Bug status of WW06 could be found
on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mai
Hi all,
The overall open bug trend did not change a lot in last 3 weeks. WDD
number and Open Bug number are 702 and 141. Bug status of WW03 could be found
on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto ma
Hi all,
The overall open bug trend increased a little last week. The new
submitted bug vs. fixed bug number is 17 vs. 21. WDD number is 675. Bug status
of WW02 could be found on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
Hi all,
The overall open bug trend decreases a lot last week. The new submitted
bug vs. fixed bug number is 3 vs. 22. WDD number is 641. Bug status of WW01
could be found on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
The overall open bug trend keeps flat last week. The new submitted bug
vs. fixed bug number is 7 vs. 5. WDD number keeps at 684. Bug status of WW53
could be found on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
I think we could skip these tests on QEMU. Some boards do not have enough
memory or power CPU for LTP/POSIX testing. That's why we tested QEMU at the
beginning.
Yi could help to clarify.
> Hi All,
>
> I am fixing failed test cases of POSIX tests, and I meet some cases
> just fail on qemu platfo
Hi all,
The overall open bug trend increased a little last week. The new
submitted bug vs. fixed bug number is 24 vs. 18. Open bug and WDD number
decreased to 141 and 681. Bug status of WW52 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Thanks a lot for testing and reporting, Wolfgang.
I will include this into final test report.
> Dear Jiajun Hu,
>
> In message
> ntel.com> you wrote:
>>
>>
>> This is the weekly test report for Yocto 1.2 M1 RC2 build. There are
>> 2 new bugs found for this build. HuronRiver board is broken, so
Hi all,
The overall open bug trend decreased last week. The new submitted bug
vs. fixed bug number is 22 vs. 31. Open bug and WDD number decreased to 134 and
658. Bug status of WW51 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
The overall open bug trend increased a little last week. The new
submitted bug vs. fixed bug number is 14 vs. 9. Open bug and WDD number
decreased to 142 and 702. Bug status of WW50 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
_
Hi all,
The overall open bug trend does not change a lot last week. The new
submitted bug vs. fixed bug number is 22 vs. 18. Open bug and WDD number
decreased to 139 and 687. Bug status of WW49 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
_
Hi all,
The overall open bug trend decreased a lot last week. The new submitted
bug vs. fixed bug number is 11 vs. 37. Open bug and WDD number decreased to 138
and 682. Bug status of WW48 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
Core Team Meeting:
Shane, Dongxiao, Edwin, Dexuan, Lianhao, Saul, Beth, ScottG, Robert, Nitin,
Jiajun
Scribe: Jiajun
1.2 Status
---
- Review the Yocto Project Status @
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status, "Feature Board"
is used to track feature status and "
Hi all,
The overall open bug trend does not change a lot last week. Open bug
and WDD number increased to 164 and 825. Bug status of WW47 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailin
Hi all,
The overall open bug trend continue increasing last week. Open bug and
WDD number increased to 165 and 846. Bug status of WW46 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailing
Hi all,
The overall open bug trend continue increasing last week. Open bug and
WDD number increased to 165 and 841. Bug status of WW45 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailing
Hi all,
I have a test with Richard's recent patch to improve build performance -
"gettext: Switch to disabling nls and reducing -native build dependencies to a
set of pre built m4 macros",
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b090fde5c184a64d3dd77c5f87b9596854e272ec.
With the pa
Hi all,
The overall open bug trend increased last week. Open bug and WDD number
increased to 156 and 781. Bug status of WW44 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mailing list
yocto
We also test 1.1 on a 4-core Core i7 machine with 4GB memory. The build time is
about 120 minutes. The detailed test result and configuration is on
https://wiki.yoctoproject.org/wiki/Performance_Test. Maybe you could follow the
page and retry the build.
> What machine are you using (amount of r
Hi all,
The overall open bug trend keep flat last week. Open bug and WDD number
increased to 140 and 699. Yocto 1.1 released last week. Bug status of WW43
could be found on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
__
Hi all,
The overall open bug trend increased a little last week. Open bug and
WDD number increased to 141 and 699. QA finished 1.1 M4 RC4 testing. Bug status
of WW42 could be found on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
Hi all,
The overall open bug trend continued decreasing during last 2 weeks.
There are 100+ enhancement bugs reported for 1.2 plan. Open bug number
decreased to 130. WDD number decreased to 642. QA is working on 1.1 M4 RC4
testing. Bug status of WW41 could be found on
https://wiki.yocto
Hi all,
The overall open bug trend continued increasing last week. The
new-submit vs. fixed bug is 30 vs. 21. Open bug number increased to 136. WDD
number increased to 683. QA finished RC2 testing and there are still some open
issues for hob and multi-lib. Bug status of WW39 could be fou
Hi all,
The overall open bug trend increased a little last week. The new-submit
vs. fixed bug is 23 vs. 16. Open bug number increased to 130. WDD number
increased to 655. M4 RC2 build does not 100% pass. Bug status of WW38 could be
found on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Tr
Hi all,
The overall open bug trend kept decreasing last week. The new-submit
vs. fixed bug is 20 vs. 31. Open bug number decreased to 121. WDD number
decreased to 616. Bug status of WW37 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
_
Hi all,
The overall open bug trend keep flat last week. The new-submit vs.
fixed bug is 27 vs. 30. Open bug number decreased to 134. WDD number decreased
to 674. Bug status of WW36 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
Hi all,
The overall open bug trend continue to decrease last week. The
new-submit vs. fixed bug is 35 vs. 40. Open bug number decreased to 136. WDD
number decreased to 675, which is close to the number of 1.0 release. Bug
status of WW35 could be found on
https://wiki.yoctoproject.org/wi
> Hi all,
>
> We now have the mechanism for fixing bug #1096 [1] i.e. showing a
> warning if the user is running a build on a distro that has not been
> tested; however to make this work what we now need is a list of
> distributions we want to consider tested. What distros specifically are we
> g
Hi all,
The overall open bug trend goes down last week. The new-submit vs.
fixed bug is 20 vs. 33. Open bug number decreased to 146. WDD number decreased
to 739. Bug status of WW34 could be found on
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
Hi all,
Last week QA finished M3 RC3 testing. The new-submit vs. fixed bug is
18 vs. 39. A lot of bugs are got fixed. Open bug number decreased to 157. WDD
number decreased to 800. Bug status of WW33 could be found on
https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
Last week is for M3 stabilization. The new-submit vs. fixed bug is 43
vs. 42. Open bug number increased to 178. WDD number increased to 921. Bug
status of WW32 could be found on
https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
Hi all,
Yocto 1.1 M2 released last week. The new-submit vs. fixed bug is 28 vs.
36. A lot of bugs are fixed, which make both open bug number and WDD number
decreased a lot -- Open bug number from 185 to 174; WDD number from 943 to 887.
Bug status of WW30 could be found on
https://wiki.p
Hi all,
RC3 is built out last week and QA is testing it. The new-submit vs.
fixed bug is 26 vs. 24 for last week. The open bug number increased to 185 (No
enhancement bugs counted). WDD number increased from 933 to 943. Several
Critical and Major bugs are fixed in RC3. Meanwhile, a lot o
Hi all,
Last week QA finished testing for M2 RC2. The new-submit vs. fixed bug
is 20 vs. 10 for last week. The open bug number increased to 182 (No
enhancement bugs counted). WDD number increased a lot, from 866 to 933. Several
Critical and Major bugs are found in RC2 testing. Bug status
> In our technical team call today we spent some time discussing how to
> support distribution releases that are due to happen around the time of Yocto
> 1.1.
>
> Yocto 1.1 is scheduled for release on October 6th[1], the same month
> in which both Ubuntu and Fedora have new releases planned[2,3].
Hi all,
Last week is for Yocto 1.1 M2 stabilization. QA finished testing for M2
RC1. The new-submit vs. fixed bug is 22 vs. 23 for last week. The open bug
number stays at 171(No enhancement bugs counted). WDD number decreased from 878
to 866. Yocto 1.1 M2 RC1 build is coming. Bug status
Hi all,
The new-submit vs. fixed bug is 14 vs. 20 for last week. The open bug
number decreased, from 174 to 171(No enhancement bugs counted). WDD number
decreased from 898 to 878. Yocto 1.1 M2 RC1 build is coming. QA will validate
it this week. Bug status of WW27 could be found on
https
Hi all,
From this week, a new chart is introduced -- Open bug Trend by
Severity. This chart shows latest open bug number by severity and does not take
Enhancement bug into account. We will use the number from now instead of total
open bug number in bugzilla. The number of last week is 17
Hi all,
The open bug number of last week increased to 221. And the weight
number of all open bugs increased to 887. QA recovered weekly testing for
upstream. Bug status of WW25 could be found on
https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
_
Hi all,
The open bug number of last week increased to 210. QA finished Yocto
1.1 M1 testing with no critical bugs open now. Bug status of WW24 could be
found on https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yocto mai
> On 06/06/2011 09:36 PM, Xu, Jiajun wrote:
>> Hi all,
>>
>> This is the fullpass test report for Yocto 1.1 M1 RC2 build. There are
>> 3 new bugs found in this testing compared with weekly testing.
>> Non-GPLv3 build could not work and one new LTP failure foun
Hi all,
The open bug number of last week decreased to 199. QA is performing
fullpass testing against Yocto 1.1 M1 RC2 build. The 2 block issues for
beagleboard are fixed. Bug status of WW23 could be found on
https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
Hi all,
The open bug number of last week increased to 203, which is the highest
number in our project. QA is doing validation for Yocto 1.1 M1 builds. Bug
status of WW22 could be found on
https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
_
Hi all,
The open bug number of last week increased to 186. QA finished 1.0.1
testing and finally no critical bug exist for 1.0.1. Bug status of WW21 could
be found on https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
Best Regards,
Jiajun
___
yo
Hi all,
From this week, QA will maintain a wiki page to save weekly bug trend
charts for Yocto. The wiki page URL is
https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend. There are lots of bugs are
fixed in WW20, while more new bugs are submitted. The open bug number increased
to 180. Weekly
> All,
>
> The current nightly based on d82f205cfa790b40e132e11b7937050bc3b97ff3
> is showing 3 build failures so far.
>
> Machine: qemux86
> Failure: intermittent tasks_0.18 failure at do_compile
> Description: Tasks_0.18 has failed during one buildset, however it's
> not failing on the other.
>
> I've made a few changes to the autobuilder that people should know about.
> Currently, we've been utilizing the milestone builders to split the
> nightly to both the internal and external builders in order to speed
> things up. I've renamed them to nightly-internal* and
> nightly-external*. They
> On Thu, 2010-12-23 at 14:08 -0800, Flanagan, Elizabeth wrote:
>> Next, the following bugs have been making it difficult to track down
>> build failures:
>>
>> Sanity Test Boot test returns invalid results.
>> http://bugzilla.pokylinux.org/show_bug.cgi?id=611
>
> Fixes for #611, #612 and some o
> On Sun, Dec 12, 2010 at 9:10 PM, Xu, Jiajun wrote:
>>> [Resend with correct mailing lists]
>>>
>>>
>>> Yocto / Poky Folks:
>>>
>>> Thanks to everyone's hard work, we are currently on working getting
>>> the first buil
> [Resend with correct mailing lists]
>
>
> Yocto / Poky Folks:
>
> Thanks to everyone's hard work, we are currently on working getting
> the first build of M2 started and available for QA testing on Monday.
>
> I have pushed out the lastest commit that was pending in the
> distro/master area t
Hi all,
This is the Weekly Test Report for nightly build 20101204. Toolchain and
qemuppc sdk testing is blocked because build for them failed. Netbook testing
is also blocked because of a new installation bug.
Other failed cases are caused by known bugs in bugzilla. Zypper still
>
> I wanted to give people a heads up about the addition of a few more
> targets to the nightly build and how they'll effect the nightly (and our
> overall efficency).
>
> This bug asks for the addition of a few targets:
>
> arm: beagleboard: poky-image-sato, poky-image-minimal, poky-image-sdk
73 matches
Mail list logo
