|
Re: Did not find big problems for today's Rc4 (x86/arm) toolchain sdk related images
I didthe SDK part test of RC4a images on qemuppc, qemumips, and BlackSand. No newbugs found compared to the test of RC3.
Best Regards,
-Lianhao
From:yocto-bounces@...
I didthe SDK part test of RC4a images on qemuppc, qemumips, and BlackSand. No newbugs found compared to the test of RC3.
Best Regards,
-Lianhao
From:yocto-bounces@...
|
By
Lu, Lianhao <lianhao.lu@...>
·
#128
·
|
|
Did not find big problems for today's Rc4 (x86/arm) toolchain sdk related images
FYI. SDK/toolchain part behaves well from RC4.
Thanks
Kevin
FYI. SDK/toolchain part behaves well from RC4.
Thanks
Kevin
|
By
Tian, Kevin <kevin.tian@...>
·
#127
·
|
|
Test Report for Yocto M4 20101024 Build
Hi all,
This is the PartialTest Report for M4 build 20101024(RC4a). Thanks for Dexuan’s help ontesting. We finished most testing for IA targets. There is no regression issuefound. 2 new
Hi all,
This is the PartialTest Report for M4 build 20101024(RC4a). Thanks for Dexuan’s help ontesting. We finished most testing for IA targets. There is no regression issuefound. 2 new
|
By
Xu, Jiajun <jiajun.xu@...>
·
#132
·
|
|
Poky weekly bug trend charts -- WW43
Hi all,
This is the Poky weekly bug trend charts for last week (WW43). The open bug number increased to 128. 22 bugs are marked as fixed in last week.
The 1st chart indicates the total open bug
Hi all,
This is the Poky weekly bug trend charts for last week (WW43). The open bug number increased to 128. 22 bugs are marked as fixed in last week.
The 1st chart indicates the total open bug
|
By
Xu, Jiajun <jiajun.xu@...>
·
#126
·
|
|
Re: RC3 vs RC4a
QA will try as more as possible and send out result today.
Best Regards,
Jiajun
QA will try as more as possible and send out result today.
Best Regards,
Jiajun
|
By
Xu, Jiajun <jiajun.xu@...>
·
#125
·
|
|
Re: RC3 vs RC4a
OK, we'll try latest RC4a and report any new issues if seen.
Thanks
Kevin
OK, we'll try latest RC4a and report any new issues if seen.
Thanks
Kevin
|
By
Tian, Kevin <kevin.tian@...>
·
#124
·
|
|
Re: RC3 vs RC4a
The build has been running overnight and should be complete, the images are in the standard location on the internal and external autobuilder dated
The build has been running overnight and should be complete, the images are in the standard location on the internal and external autobuilder dated
|
By
Saul G. Wold <sgw@...>
·
#123
·
|
|
Re: Fetcher error reporting
One poky-image-sdk-live build completed from a clean slate from inside the firewall. I have another outside the firewall that will take a bit longer, but is well on its way without any errors. Looking
One poky-image-sdk-live build completed from a clean slate from inside the firewall. I have another outside the firewall that will take a bit longer, but is well on its way without any errors. Looking
|
By
Darren Hart <dvhart@...>
·
#122
·
|
|
Re: Fetcher error reporting
I've applied and am running another build. This looks sane to me. If I still run into this, I think the next step is to do a brute force zero-length test, and throw the FetchError and take this
I've applied and am running another build. This looks sane to me. If I still run into this, I think the next step is to do a brute force zero-length test, and throw the FetchError and take this
|
By
Darren Hart <dvhart@...>
·
#121
·
|
|
Re: Fetcher error reporting
We've talked about this a lot over jabber. We don't have a reproducer.
What we do see is its always the wget fetcher that hits this (for mirror
urls in the case of git repos) and its failing creating
We've talked about this a lot over jabber. We don't have a reproducer.
What we do see is its always the wget fetcher that hits this (for mirror
urls in the case of git repos) and its failing creating
|
By
Richard Purdie <rpurdie@...>
·
#120
·
|
|
RC3 vs RC4a
We have an RC3 which we feel confident in based on our no-nogo launch decision.
However, there are a handful of issues which are not critical but would be desirable to address them - for example,
We have an RC3 which we feel confident in based on our no-nogo launch decision.
However, there are a handful of issues which are not critical but would be desirable to address them - for example,
|
By
David Stewart
·
#119
·
|
|
Re: Last minute changes - Review Request
Saul and Richard and I put a plan together for this, will create a new thread for it.
Saul and Richard and I put a plan together for this, will create a new thread for it.
|
By
David Stewart
·
#118
·
|
|
Re: RFC: "Demo Use Cases" documentation for the web page
Figured I should expand this..
Freescale MPC8315E-RDB (I think w/ have the 'A' revision, but thats not likely important)
Figured I should expand this..
Freescale MPC8315E-RDB (I think w/ have the 'A' revision, but thats not likely important)
|
By
Mark Hatle <mark.hatle@...>
·
#115
·
|
|
Re: RFC: "Demo Use Cases" documentation for the web page
arm - beagleboard (I don't know the revision)
ppc - fsl-mpc8315e-rdb
mips - Ubiquity Networks Router Station Pro a.k.a. MIPS Linux Starter Kit
arm - beagleboard (I don't know the revision)
ppc - fsl-mpc8315e-rdb
mips - Ubiquity Networks Router Station Pro a.k.a. MIPS Linux Starter Kit
|
By
Mark Hatle <mark.hatle@...>
·
#114
·
|
|
Re: RFC: "Demo Use Cases" documentation for the web page
OK, so can someone provide me with an appropriate list of the non-IA platforms? I know them as "The MIPS board" "The PPC board" etc.
--
Darren Hart
Embedded Linux Kernel
OK, so can someone provide me with an appropriate list of the non-IA platforms? I know them as "The MIPS board" "The PPC board" etc.
--
Darren Hart
Embedded Linux Kernel
|
By
Darren Hart <dvhart@...>
·
#113
·
|
|
RFC V2: "Demo Use Cases" documentation for the web page
Apologies for the resend, sent from the wrong address and the list bounced it.
Version 2 with some updates from Kevin, Dave, Tom, and Mark:
Media Network Demo
==================
The Yocto Project
Apologies for the resend, sent from the wrong address and the list bounced it.
Version 2 with some updates from Kevin, Dave, Tom, and Mark:
Media Network Demo
==================
The Yocto Project
|
By
Darren Hart <dvhart@...>
·
#112
·
|
|
Re: RFC: "Demo Use Cases" documentation for the web page
Yeah, I think we should. It proves that it really does run on other hardware, and the demo hw is the example. Showing product names helps shake the image that this is IA-only.
- A
--
Alex
Yeah, I think we should. It proves that it really does run on other hardware, and the demo hw is the example. Showing product names helps shake the image that this is IA-only.
- A
--
Alex
|
By
Alex deVries <alex.devries@...>
·
#111
·
|
|
Re: RFC: "Demo Use Cases" documentation for the web page
Hrm... do we want to explicitly call them out? The point is that it was multi-architecture, but for some to recreate it, the point is that it doesn't really matter what hardware they have - poky can
Hrm... do we want to explicitly call them out? The point is that it was multi-architecture, but for some to recreate it, the point is that it doesn't really matter what hardware they have - poky can
|
By
Darren Hart <dvhart@...>
·
#110
·
|
|
Fetcher error reporting
Richard,
Here is an example of the do_fetch/do_unpack failure that I believe is representative of what Dirk saw and what I have been seeing periodically.
I saw the following while building libproxy
Richard,
Here is an example of the do_fetch/do_unpack failure that I believe is representative of what Dirk saw and what I have been seeing periodically.
I saw the following while building libproxy
|
By
Darren Hart <dvhart@...>
·
#109
·
|
|
Re: "Demo Use Cases" documentation for the web page
/media/storage is the export location...
/media/storage is the export location...
|
By
Mark Hatle <mark.hatle@...>
·
#108
·
|