Date   

Re: Race condition when building a recipe and poky-image-minimal-initramfs

Xu, Dongxiao <dongxiao.xu@...>
 

Mark Hatle wrote:
On 3/14/11 8:47 PM, Xu, Dongxiao wrote:
Hi Richard,
There was already a defect covering this. The bug number is "797".

In order to fix the problem a lock was added to the RPM generation.
This lock should be preventing both RPM package generation and rootfs
construction from running at the same time.

The code was checked into Bernard on 2011-03-10. If your image is
from after that date, please reopen the defect and add the details
below.
Yes, thanks for pointing it out. The phenomenon is similar as bug 797. I will mark it as a duplication.

Just checked that, your fixing patch for 797 is already in my build. Therefore I will re-open the bug.

My build is based on commit 43a2d098008eee711399b8d64594d84ae034b9bf.

In my side, the race condition is happened in manifest generation while executing "package_update_index_rpm()".

Thanks,
Dongxiao


--Mark

These days I found a race condition between building a recipe and
poky-image-minimal-initramfs, to reproduce it, you can try as:

1) Run "bitbake poky-image-sato-live". Build the full sato-live
image until it is successful. 2) Bump connman's PR (or some other
sato recipe's PR). 3) Rebuild the sato live image by "bitbake
poky-image-sato-live".

Sometimes, I meet build error like the following, however it does
not happen every time.

-------------------------------------------------------
Generating solve db for
/distro/dongxiao/build-qemux86/tmp/deploy/rpm/qemux86... total:
1 0.000000 MB 1.424841 secs fingerprint: 1020
0.006796 MB 0.033057 secs install: 340
0.000000 MB 0.371773 secs dbadd: 340
0.000000 MB 0.362746 secs dbget: 2196
0.000000 MB 0.004278 secs dbput: 340
1.504908 MB 0.308950 secs readhdr: 3401
2.961280 MB 0.005603 secs hdrload: 1700
4.389932 MB 0.007001 secs hdrget: 57535
0.000000 MB 0.043769 secs
Generating solve db for
/distro/dongxiao/build-qemux86/tmp/deploy/rpm/i586...
error: open of
/distro/dongxiao/build-qemux86/tmp/deploy/rpm/i586/connman-plugin-ethe
rnet-0.65-r4.i586.rpm failed: No such file or directory
rpm.real: ./rpmio_internal.h:190: fdGetOPath: Assertion `fd !=
((void *)0) && fd->magic == 0x04463138' failed.
/distro/dongxiao/build-qemux86/tmp/work/qemux86-poky-linux/poky-image-minimal-initramfs-1.0-r0/temp/run.do_rootfs.468:
line 375: 669 Aborted rpm --dbpath /var/lib/rpm
--define='_openall_before_chroot 1' -i --replacepkgs --replacefiles
--oldpackage -D "_dbpath $pkgdir/solvedb" --justdb --noaid --nodeps
--noorder --noscripts --notriggers --noparentdirs --nolinktos
--stats --ignoresize --nosignature --nodigest -D "__dbi_txn create
nofsync" $pkgdir/solvedb/manifest ERROR: Function 'do_rootfs' failed
(see
/distro/dongxiao/build-qemux86/tmp/work/qemux86-poky-linux/poky-image-
minimal-initramfs-1.0-r0/temp/log.do_rootfs.468 for further
information)
-------------------------------------------------------

The root cause for this issue should be,
poky-image-minimal-initramfs's do_rootfs task doesn't have
dependency on connman, thus their tasks will be run simultaneously.
Poky-image-minimal-initramfs's do_rootfs will call
"rootfs_rpm_do_rootfs" --> "package_update_index_rpm", where it will
update all the packages depsolver db in ${DEPLOY_DIR_RPM}.

When the package_update_index_rpm function is handling connman's rpm
package, and at the same time, connman is removing old rpm and
trying to generate a new one (e.x, from r4 to r5), then the build
error will occur, saying that it could not find r4 version of
connman-plugin-ethernet...

One choice may be to force poky-image-minimal-initramfs's do_rootfs
to depends on all recipe's do_package to ensure correctness, even
though it only depends on some basic recipes.

However I think it is not such elegant.

Do you have ideas on it?

BTW, I will file a bug 867 to track this issue.
http://bugzilla.pokylinux.org/show_bug.cgi?id=867

Thanks,
Dongxiao
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: Race condition when building a recipe and poky-image-minimal-initramfs

Mark Hatle <mark.hatle@...>
 

On 3/14/11 8:47 PM, Xu, Dongxiao wrote:
Hi Richard,
There was already a defect covering this. The bug number is "797".

In order to fix the problem a lock was added to the RPM generation. This lock
should be preventing both RPM package generation and rootfs construction from
running at the same time.

The code was checked into Bernard on 2011-03-10. If your image is from after
that date, please reopen the defect and add the details below.

--Mark

These days I found a race condition between building a recipe and poky-image-minimal-initramfs, to reproduce it, you can try as:

1) Run "bitbake poky-image-sato-live". Build the full sato-live image until it is successful.
2) Bump connman's PR (or some other sato recipe's PR).
3) Rebuild the sato live image by "bitbake poky-image-sato-live".

Sometimes, I meet build error like the following, however it does not happen every time.

-------------------------------------------------------
Generating solve db for /distro/dongxiao/build-qemux86/tmp/deploy/rpm/qemux86...
total: 1 0.000000 MB 1.424841 secs
fingerprint: 1020 0.006796 MB 0.033057 secs
install: 340 0.000000 MB 0.371773 secs
dbadd: 340 0.000000 MB 0.362746 secs
dbget: 2196 0.000000 MB 0.004278 secs
dbput: 340 1.504908 MB 0.308950 secs
readhdr: 3401 2.961280 MB 0.005603 secs
hdrload: 1700 4.389932 MB 0.007001 secs
hdrget: 57535 0.000000 MB 0.043769 secs
Generating solve db for /distro/dongxiao/build-qemux86/tmp/deploy/rpm/i586...
error: open of /distro/dongxiao/build-qemux86/tmp/deploy/rpm/i586/connman-plugin-ethernet-0.65-r4.i586.rpm failed: No such file or directory
rpm.real: ./rpmio_internal.h:190: fdGetOPath: Assertion `fd != ((void *)0) && fd->magic == 0x04463138' failed.
/distro/dongxiao/build-qemux86/tmp/work/qemux86-poky-linux/poky-image-minimal-initramfs-1.0-r0/temp/run.do_rootfs.468: line 375: 669 Aborted rpm --dbpath /var/lib/rpm --define='_openall_before_chroot 1' -i --replacepkgs --replacefiles --oldpackage -D "_dbpath $pkgdir/solvedb" --justdb --noaid --nodeps --noorder --noscripts --notriggers --noparentdirs --nolinktos --stats --ignoresize --nosignature --nodigest -D "__dbi_txn create nofsync" $pkgdir/solvedb/manifest
ERROR: Function 'do_rootfs' failed (see /distro/dongxiao/build-qemux86/tmp/work/qemux86-poky-linux/poky-image-minimal-initramfs-1.0-r0/temp/log.do_rootfs.468 for further information)
-------------------------------------------------------

The root cause for this issue should be, poky-image-minimal-initramfs's do_rootfs task doesn't have dependency on connman, thus their tasks will be run simultaneously. Poky-image-minimal-initramfs's do_rootfs will call "rootfs_rpm_do_rootfs" --> "package_update_index_rpm", where it will update all the packages depsolver db in ${DEPLOY_DIR_RPM}.

When the package_update_index_rpm function is handling connman's rpm package, and at the same time, connman is removing old rpm and trying to generate a new one (e.x, from r4 to r5), then the build error will occur, saying that it could not find r4 version of connman-plugin-ethernet...

One choice may be to force poky-image-minimal-initramfs's do_rootfs to depends on all recipe's do_package to ensure correctness, even though it only depends on some basic recipes.

However I think it is not such elegant.

Do you have ideas on it?

BTW, I will file a bug 867 to track this issue. http://bugzilla.pokylinux.org/show_bug.cgi?id=867

Thanks,
Dongxiao
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Race condition when building a recipe and poky-image-minimal-initramfs

Xu, Dongxiao <dongxiao.xu@...>
 

Hi Richard,

These days I found a race condition between building a recipe and poky-image-minimal-initramfs, to reproduce it, you can try as:

1) Run "bitbake poky-image-sato-live". Build the full sato-live image until it is successful.
2) Bump connman's PR (or some other sato recipe's PR).
3) Rebuild the sato live image by "bitbake poky-image-sato-live".

Sometimes, I meet build error like the following, however it does not happen every time.

-------------------------------------------------------
Generating solve db for /distro/dongxiao/build-qemux86/tmp/deploy/rpm/qemux86...
total: 1 0.000000 MB 1.424841 secs
fingerprint: 1020 0.006796 MB 0.033057 secs
install: 340 0.000000 MB 0.371773 secs
dbadd: 340 0.000000 MB 0.362746 secs
dbget: 2196 0.000000 MB 0.004278 secs
dbput: 340 1.504908 MB 0.308950 secs
readhdr: 3401 2.961280 MB 0.005603 secs
hdrload: 1700 4.389932 MB 0.007001 secs
hdrget: 57535 0.000000 MB 0.043769 secs
Generating solve db for /distro/dongxiao/build-qemux86/tmp/deploy/rpm/i586...
error: open of /distro/dongxiao/build-qemux86/tmp/deploy/rpm/i586/connman-plugin-ethernet-0.65-r4.i586.rpm failed: No such file or directory
rpm.real: ./rpmio_internal.h:190: fdGetOPath: Assertion `fd != ((void *)0) && fd->magic == 0x04463138' failed.
/distro/dongxiao/build-qemux86/tmp/work/qemux86-poky-linux/poky-image-minimal-initramfs-1.0-r0/temp/run.do_rootfs.468: line 375: 669 Aborted rpm --dbpath /var/lib/rpm --define='_openall_before_chroot 1' -i --replacepkgs --replacefiles --oldpackage -D "_dbpath $pkgdir/solvedb" --justdb --noaid --nodeps --noorder --noscripts --notriggers --noparentdirs --nolinktos --stats --ignoresize --nosignature --nodigest -D "__dbi_txn create nofsync" $pkgdir/solvedb/manifest
ERROR: Function 'do_rootfs' failed (see /distro/dongxiao/build-qemux86/tmp/work/qemux86-poky-linux/poky-image-minimal-initramfs-1.0-r0/temp/log.do_rootfs.468 for further information)
-------------------------------------------------------

The root cause for this issue should be, poky-image-minimal-initramfs's do_rootfs task doesn't have dependency on connman, thus their tasks will be run simultaneously. Poky-image-minimal-initramfs's do_rootfs will call "rootfs_rpm_do_rootfs" --> "package_update_index_rpm", where it will update all the packages depsolver db in ${DEPLOY_DIR_RPM}.

When the package_update_index_rpm function is handling connman's rpm package, and at the same time, connman is removing old rpm and trying to generate a new one (e.x, from r4 to r5), then the build error will occur, saying that it could not find r4 version of connman-plugin-ethernet...

One choice may be to force poky-image-minimal-initramfs's do_rootfs to depends on all recipe's do_package to ensure correctness, even though it only depends on some basic recipes.

However I think it is not such elegant.

Do you have ideas on it?

BTW, I will file a bug 867 to track this issue. http://bugzilla.pokylinux.org/show_bug.cgi?id=867

Thanks,
Dongxiao


Re: [oe] Collab Summit + ELC + TSC Meeting

Tom King <ka6sox@...>
 


I will be

TK

On Mon, Mar 14, 2011 at 6:15 PM, Philip Balister <philip@...> wrote:
On 03/14/2011 08:44 PM, Jeff Osier-Mixon wrote:

There also was a request for more general purpose OEDAM over the weekend,
maybe in parallel or before/after TSC meeting:

Any thoughts on that?

Most of the replies there are from TSC people who are going to be there
with the exceptions of yourself and Mike. I'm ok with having a more
general meeting if the demand is there and Jefro can arrange it. If
there are only a few people, I'd suggest something like meeting after
the TSC meeting and finding food/drink together.



For those who don't know me, I'm Jefro.  :)

As Richard says, a small crowd would probably interact better over
refreshments.  If you are interested in such a gathering, send me a note at
jefro@... and let me know when you are available, and I'll see what I
can pull together.

A quick show of hands, how many OE people can be in San Francisco over the weekend of April 9-10? TSC people, go ahead and chime in for completeness.

Philip


_______________________________________________
Openembedded-members mailing list
Openembedded-members@...
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members


Re: [oe] Collab Summit + ELC + TSC Meeting

Philip Balister
 

On 03/14/2011 08:44 PM, Jeff Osier-Mixon wrote:

There also was a request for more general purpose OEDAM over the weekend,
maybe in parallel or before/after TSC meeting:

Any thoughts on that?
Most of the replies there are from TSC people who are going to be there
with the exceptions of yourself and Mike. I'm ok with having a more
general meeting if the demand is there and Jefro can arrange it. If
there are only a few people, I'd suggest something like meeting after
the TSC meeting and finding food/drink together.

For those who don't know me, I'm Jefro. :)

As Richard says, a small crowd would probably interact better over
refreshments. If you are interested in such a gathering, send me a note at
jefro@... and let me know when you are available, and I'll see what I
can pull together.
A quick show of hands, how many OE people can be in San Francisco over the weekend of April 9-10? TSC people, go ahead and chime in for completeness.

Philip


Re: [oe] Collab Summit + ELC + TSC Meeting

Jeff Osier-Mixon <jefro@...>
 

> There also was a request for more general purpose OEDAM over the weekend,
> maybe in parallel or before/after TSC meeting:
>
> Any thoughts on that?

Most of the replies there are from TSC people who are going to be there
with the exceptions of yourself and Mike. I'm ok with having a more
general meeting if the demand is there and Jefro can arrange it. If
there are only a few people, I'd suggest something like meeting after
the TSC meeting and finding food/drink together.


For those who don't know me, I'm Jefro.  :)

As Richard says, a small crowd would probably interact better over refreshments.  If you are interested in such a gathering, send me a note at jefro@... and let me know when you are available, and I'll see what I can pull together.

-- 
Jeff Osier-Mixon
Yocto Community Manager @Intel


Yocto Release Tracking Meeting - Tuesday, March 15th, 8am Pacific

Fleischer, Julie N <julie.n.fleischer@...>
 

We are entering the final phases of Yocto 1.0 and plan to have another Release Tracking meeting on Tuesday at 8am Pacific (recall that the US just moved our clocks forward an hour on Sunday). Details are below:

Time/Date: Tuesday, March 15, 2011, 08:00 AM US Pacific Time
Dial in: 916-356-2663, 8-356-2663, Bridge: 1, Passcode: 7363183

Agenda:
1) New Introductions
2) Review Yocto 1.0 Release Criteria - https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.0_Release_Criteria
3) Opens/Risks

-----------------------
Julie Fleischer
Open Source Technology Center
Intel Corporation


Post 1.0 Feature Planning and Collab Summit/ELC

Richard Purdie
 

Hi,

The Yocto Project is in the final stages of the 1.0 release. This means
its time to kick off the post 1.0 planning process and see what things
we think we should be targeting for the release after this.

The various teams involved have been keeping a track of their ideas as
we went through 1.0 and Julie was kind enough to create a post 1.0 list
on the wiki based on these ideas:

https://wiki.yoctoproject.org/wiki/Yocto_1.1_Features

(note whilst this says 1.1, the version number is just a working title
for post 1.0).

There are some general things we're trying to work on in Yocto listed on
https://wiki.yoctoproject.org/wiki/Yocto_General_Features and also some
general themes we're considering for the post 1.0 release which are at
the top of the above features page.

I'd like to invite people from the community to propose ideas.
Indicating whether its something you'd be prepared to work on yourself
or would like the project to consider would be helpful.

I'd also like to invite our Yocto partners to look at this list and see
what they'd add or prioritise and considering putting resources into.

Since its a wiki, people can add to it, or people can reply to this
email and start a thread for discussion.

On this topic, I'd like to invite interested parties to the Linux
Foundation Collaboration Summit
(http://events.linuxfoundation.org/events/collaboration-summit). As well
as various Yocto partner focused sessions, there will be a Yocto
specific technical time slot on the agenda for technical discussion
where I'd be happy to see the community represented (partner's are being
invited to bring their technical people for that). In that session I'm
hoping to discuss the post 1.0 plans amongst other topics.

The Embedded Linux Conference is the following week so if you're
attending that there will be a similar Yocto/OE BoF session there which
will cover similar topics and you can attend instead if you'll be at
ELC.

Cheers,

Richard


Re: Eclipse plug-in does not detect my target

Leon Woestenberg <leon.woestenberg@...>
 

Hello Jessica,

On Sun, Mar 13, 2011 at 12:55 AM, Zhang, Jessica
<jessica.zhang@...> wrote:
Leon Woestenberg wrote:
built, I wanted to test the Eclipse plug-in. After selecting Poky Tree
mode in the Yocto Tool configuration, I could not make it detect the
target; the drop down box remained empty.
Did you run "bitbake meta-ide-support", the eclipse plug-in will detect the
target architecture based on the environment script file under the toolchain
root location, e.g. build/tmp/environment-setup-i586-poky-linux.
No I didn't. I will continue to work on this end of this week. Thanks,

Regards,
--
Leon


Fullpass Test Report for Yocto M4 RC2 20110305 Build

Xu, Jiajun <jiajun.xu@...>
 

Hi all,

       This is the fullpass test report for RC2 build 20110305. This build has a better quality than RC1. We have 5 blocked issues for RC2: no emgd crownbay image on autobuilder sharing folder; n450 image fails to boot on blacksand; sato-sdk image build failed for qemuppc; i686 toolchain not copied into sharing folder on autobuilder; No LSB image provided for meta-intel BSP. For the other testing targets, except for zypper function, most components could work well. For poky, sstate and non-gplv3 build still do not work correctly.

       For bug fixing, the zypper search issue is fixed on qemux86-64 platform. The x11vnc icon click no response issue is also fixed.

 

Test Summary

---------------------------------------

Test Result Summary

Component

Target

Status

Comments

BSP

SugarBay

GOOD

Only partial zypper function not work 2D & 3D benchmarks run well on it

 

CrownBay

BLOCK

No emgd crownbay image available; noemgd image works well

 

JasperForest

GOOD

Only partial zypper function not work

 

Blacksand

BLOCK

n450 image fail to boot on blacksand

 

Beagleboard

GOOD

Only one RTC issue exists

 

Routerstationpro

GOOD

Only partial zypper function not work

 

Mpc8315e-rdb

GOOD

Only partial zypper function not work

QEMU

qemux86

GOOD

Only partial zypper function not work

 

qemux86-64

GOOD

zypper search segfault (bug 721) is fixed

 

qemuarm

GOOD

Only partial zypper function not work

 

qemuppc

BLOCK

sato-sdk image build failed on autobuilder

 

qemumips

BUGGY

zypper segfault with this target; vnc client not pop-up fixing patch is not in this commit yet.

Poky

 

BUGGY

sstate and non-gplv3 build do not work correctly

Documentation

 

GOOD

 

SDK

 

BLOCK

meta-ide-support not buildable with distro/bernard branch; unfs not work for qemuppc; i686 toolchain are not copied to sharing folder;

Complience Test

 

In testing

LTP and POSIX testing is not finished yet, will be ready on wiki later.

 

 

Critical bugs, more than 50% test cases are blocked

 

 

 

Only Normal, Minor or Enhancement bugs, less than 10% test cases failed

 

 

 

Normal, Major and Critical bugs, more than 10% test cases failed

 

 

 

Detailed Test Result for each component

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Sugarbay Sato-SDK

61

0

58

3 (bug 804)

0

Jasperforest Sato-SDK

38

0

35

3 (bug 804)

0

BeagleBoard Sato

14

0

12

2 (bug 787, 767)

0

BeagleBoard Sato-SDK

23

0

21

2 (bug 787, 767)

0

Routerstationpro Sato-SDK

32

0

28

3 (bug 845, 787)

1 (bug 845)

Mpc8315e-rdb Sato-SDK

31

0

28

3 (bug 841, 787)

0

Qemux86-64 Sato

21

0

18

3 (bug 804)

0

Qemux86-64 Sato-SDK

26

0

23

3 (bug 804)

0

Qemux86 Sato

21

0

18

3 (bug 804)

0

Qemux86 Sato-SDK

26

0

23

3 (bug 804)

0

Qemumips Sato

21

0

15

3 (bug 825, 787, 782)

3 (bug 825)

Qemumips Sato-SDK

26

0

20

3 (bug 825, 787, 782)

3 (bug 825)

Qemuppc Sato

18

0

15

3 (bug 841, 787)

0

Qemuarm Sato

21

0

18

3 (bug 489, 490, 787)

0

Qemuarm Sato-SDK

26

0

23

3 (bug 489, bug 490, bug 787)

0

SDK

3

0

0

1 (bug 414, 819)

2 (i686 toolchain tarball not copied into sharing folder)

Poky

8

0

6

2 (bug 712, 788, 789)

0

Documentation

1

0

1

0

0

Total

417

0

362

46

9

 

* You can check the detailed test result in attachment for each target.

** The failed/blocked case number is listed with failed cases’ bug number.

 

Images

http://autobuilder.pokylinux.org/nightly/20110305-4/

commit: c192fefd868be53c20dfd8bc44e3e815cf53a10a

 

Issue Summary

Zypper/RPM:

1.     New! [zypper] zypper install failed on routerstationpro sdk image

http://bugzilla.pokylinux.org/show_bug.cgi?id=845

2.     New! [zypper] installation failure on ppc (nightly build 20110305-4)

http://bugzilla.pokylinux.org/show_bug.cgi?id=841

3.     New! [zypper] zypper can not search any packages after installed package by rpm on qemuarm

http://bugzilla.pokylinux.org/show_bug.cgi?id=827

4.     New! [zypper] zypper segfault in qemumips sato/sdk images

http://bugzilla.pokylinux.org/show_bug.cgi?id=825

5.     [zypper] zypper install does not work on qemux86/atom-pc

http://bugzilla.pokylinux.org/show_bug.cgi?id=803

6.     [zypper] zypper lose package information after zypper/rpm install/remove

http://bugzilla.pokylinux.org/show_bug.cgi?id=804

7.     rpm remove package error

http://bugzilla.pokylinux.org/show_bug.cgi?id=787

8.     [zypper] package removal failure

http://bugzilla.pokylinux.org/show_bug.cgi?id=491

9.     [zypper] uname –m and repo arch difference

http://bugzilla.pokylinux.org/show_bug.cgi?id=489

10.  [zypper] installation failure on arm

http://bugzilla.pokylinux.org/show_bug.cgi?id=490

 

Poky:

1.     [sstate] random error message shown when sstate is used

http://bugzilla.pokylinux.org/show_bug.cgi?id=788

2.     [sstate] only few setscene tasks run even with same build environment

http://bugzilla.pokylinux.org/show_bug.cgi?id=789

3.     Fail to build non-GPLv3 image

http://bugzilla.pokylinux.org/show_bug.cgi?id=712

 

SDK:

1.     New! meta-ide-support build fail with distro/bernard brarnch

http://bugzilla.pokylinux.org/show_bug.cgi?id=819

2.     [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS

http://bugzilla.pokylinux.org/show_bug.cgi?id=414

 

BSP:

1.     New! [meta-intel] No LSB image for meta-intel BSP

http://bugzilla.pokylinux.org/show_bug.cgi?id=849

2.     New! [n450] blacksand could not boot up with n450 BSP image

http://bugzilla.pokylinux.org/show_bug.cgi?id=837

3.     [blacksand] no sound even all options in amixer enabled

http://bugzilla.pokylinux.org/show_bug.cgi?id=798

4.     [blacksand] configured audiosink is not working for video player

http://bugzilla.pokylinux.org/show_bug.cgi?id=799

5.     [Connman] xuser must be granted privilege to start connman-applet

http://bugzilla.pokylinux.org/show_bug.cgi?id=779

6.     [Blacksand] Some error information prompted when run dmesg command

http://bugzilla.pokylinux.org/show_bug.cgi?id=607

7.     [Blacksand]system cannot enter S3 standby mode

http://bugzilla.pokylinux.org/show_bug.cgi?id=613

8.     [beagleboard] Can not set RTC correctly

http://bugzilla.pokylinux.org/show_bug.cgi?id=767

 

 

Complience:

1.     The process of installing LSB test suit and running LSB test on qemu-ppc is very slow

http://bugzilla.pokylinux.org/show_bug.cgi?id=793

2.     LSB: A test case (lib/Config.t) failed during running perl test of LSB

http://bugzilla.pokylinux.org/show_bug.cgi?id=794

3.     LSB: Some cases (libstdc++.so.6) failed on library check of LSB test

http://bugzilla.pokylinux.org/show_bug.cgi?id=795

4.     LSB: Some cases related to locale failed on libstdcpp and cpp-t2c test of LSB

http://bugzilla.pokylinux.org/show_bug.cgi?id=796

 

Others:

1.     gcc segfault on qemuppc (nightly build 20110226-1)

http://bugzilla.pokylinux.org/show_bug.cgi?id=780

2.     The vnc client does not pop-up on qemumips-sato-sdk

http://bugzilla.pokylinux.org/show_bug.cgi?id=782

 

Best Regards,

Jiajun


Re: Eclipse plug-in does not detect my target

Khem Raj
 

On 3/12/2011 3:08 PM, Leon Woestenberg wrote:
Hello Yoctonians,

I created a custom layer with the PowerPC e500v2 architecture and
machine, host tripplet "powerpc-linux-gnuspe".
maybe -gnuspe is problem ? try powerpc-linux-gnu and see if helps


After building a target package, pciutils, so that the tools were
built, I wanted to test the Eclipse plug-in. After selecting Poky Tree
mode in the Yocto Tool configuration, I could not make it detect the
target; the drop down box remained empty.

Which part of the the Eclipse plug-in code detects the target?

As per the video on YocToob(tm) I selected the build/ directory of my
installation.

Regards,


Re: Eclipse plug-in does not detect my target

Zhang, Jessica
 

Leon Woestenberg wrote:
Hello Yoctonians,

I created a custom layer with the PowerPC e500v2 architecture and
machine, host tripplet "powerpc-linux-gnuspe".

After building a target package, pciutils, so that the tools were
built, I wanted to test the Eclipse plug-in. After selecting Poky Tree
mode in the Yocto Tool configuration, I could not make it detect the
target; the drop down box remained empty.

Which part of the the Eclipse plug-in code detects the target?

As per the video on YocToob(tm) I selected the build/ directory of my
installation.
Leon,

Did you run "bitbake meta-ide-support", the eclipse plug-in will detect the
target architecture based on the environment script file under the toolchain
root location, e.g. build/tmp/environment-setup-i586-poky-linux.

- Jessica


Eclipse plug-in does not detect my target

Leon Woestenberg <leon.woestenberg@...>
 

Hello Yoctonians,

I created a custom layer with the PowerPC e500v2 architecture and
machine, host tripplet "powerpc-linux-gnuspe".

After building a target package, pciutils, so that the tools were
built, I wanted to test the Eclipse plug-in. After selecting Poky Tree
mode in the Yocto Tool configuration, I could not make it detect the
target; the drop down box remained empty.

Which part of the the Eclipse plug-in code detects the target?

As per the video on YocToob(tm) I selected the build/ directory of my
installation.

Regards,
--
Leon


Re: Please add build ID to bugs

Khem Raj
 

On 3/12/2011 8:22 AM, Darren Hart wrote:


On 03/12/2011 01:12 AM, Koen Kooi wrote:

Op 12 mrt 2011, om 09:58 heeft Darren Hart het volgende geschreven:

On 03/07/2011 11:05 AM, Jeff Osier-Mixon wrote:
Hi all

I have added the following item to the Bugzilla guidelines:

*IMPORTANT*: please include the build/commit ID as reported by BitBake,
so may be it should be termed as 'Build Configuration' instead

s/BitBake/git/ I presume?
I think he means this one:

Build Configuration:
BB_VERSION = "1.13.0"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "0671ad1"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "angstrom"
DISTRO_VERSION = "v20110312"
TARGET_FPU = "hard"
Ah, yes, that makes more sense.


Re: Please add build ID to bugs

Darren Hart <dvhart@...>
 

On 03/12/2011 01:12 AM, Koen Kooi wrote:

Op 12 mrt 2011, om 09:58 heeft Darren Hart het volgende geschreven:

On 03/07/2011 11:05 AM, Jeff Osier-Mixon wrote:
Hi all

I have added the following item to the Bugzilla guidelines:

*IMPORTANT*: please include the build/commit ID as reported by BitBake,
s/BitBake/git/ I presume?
I think he means this one:

Build Configuration:
BB_VERSION = "1.13.0"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "0671ad1"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "angstrom"
DISTRO_VERSION = "v20110312"
TARGET_FPU = "hard"
Ah, yes, that makes more sense.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: Please add build ID to bugs

Koen Kooi
 

Op 12 mrt 2011, om 09:58 heeft Darren Hart het volgende geschreven:

On 03/07/2011 11:05 AM, Jeff Osier-Mixon wrote:
Hi all

I have added the following item to the Bugzilla guidelines:

*IMPORTANT*: please include the build/commit ID as reported by BitBake,
s/BitBake/git/ I presume?
I think he means this one:

Build Configuration:
BB_VERSION = "1.13.0"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "0671ad1"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "angstrom"
DISTRO_VERSION = "v20110312"
TARGET_FPU = "hard"


regards,

Koen


Re: Please add build ID to bugs

Darren Hart <dvhart@...>
 

On 03/07/2011 11:05 AM, Jeff Osier-Mixon wrote:
Hi all

I have added the following item to the Bugzilla guidelines:

*IMPORTANT*: please include the build/commit ID as reported by BitBake,
s/BitBake/git/ I presume?

as this will help the team determine whether your bug has been fixed
already.

Guidelines are here:
https://wiki.yoctoproject.org/wiki/Community_Guidelines#Bugzilla_Guidelines

<https://wiki.yoctoproject.org/wiki/Community_Guidelines#Bugzilla_Guidelines>thanks!
--
Jeff Osier-Mixon
Yocto Community Manager @Intel



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: current status for ADT

Zhang, Jessica
 

Liping and Lianhao,

Attached is the updated 1.0 test template, feel free to add more test cases.
I think we're building RC3 over the weekend, and once the build is done, we
should test against it which contains all the latest and needed changes for
bernard. I'll monitor the build progress over the weekend and synch with you
on testing at your beginning of the week.

Thanks,
Jessica

Ke, Liping wrote:

Hi, Jessica

We use today's latest poky master which includes all our own fixes to
build (arm, i586, mips) target fs and cross toolchains. And then we
run below test:


Test environment:

1. For the available repo, use adt-installer installed toolchain:
i686-arm.

2. For meta-toolchainsdk installed toolchain: i686-i586, i686-arm,
i686-mips.

3. target: Qemu x86

Test project:

Against our selected test c++/c/libtool projects. All works fine.

All those tests are under command line with our automatic test
scripts.
We have not tested Eclipse plugin UI yet.

One thing to do is that we need to set up test adt repos for more
archs against newer changeset so that we can cover more adt-installer
tests against different archs.

Thanks & Regards,
criping


current status for ADT

Ke, Liping <liping.ke@...>
 

Hi, Jessica

We use today's latest poky master which includes all our own fixes to build
(arm, i586, mips) target fs and cross toolchains. And then we run below test:


Test environment:

1. For the available repo, use adt-installer installed toolchain: i686-arm.

2. For meta-toolchainsdk installed toolchain: i686-i586, i686-arm, i686-mips.

3. target: Qemu x86

Test project:

Against our selected test c++/c/libtool projects. All works fine.

All those tests are under command line with our automatic test scripts.
We have not tested Eclipse plugin UI yet.

One thing to do is that we need to set up test adt repos for more archs against newer changeset
so that we can cover more adt-installer tests against different archs.

Thanks & Regards,
criping


Yocto 1.0 RC2 available for download & evaluation

David Stewart
 

The Yocto Project is moving towards our 1.0 release.  The theme of this release is an improved developer experience from the Yocto 0.9 release.

 

We would love to have you download the current release candidate (RC2) and give us your feedback on bugzilla.

 

Please use http://bugzilla.yoctoproject.org to give us feedback

For questions or help, try to use the documentation or #yocto on freenode

 

Here is where to get the bits:

 

http://autobuilder.pokylinux.org/downloads/poky/poky-bernard-5.0rc2.tar.bz2

and

http://autobuilder.pokylinux.org/downloads/poky/meta-intel-bernard-5.0rc2.tar.bz2

 

Thanks!

 

Dave

Yocto Project

http://yoctoproject.org