On 01/25/2013 02:02 PM, Liu, Song wrote: > Hi Saul/Beth, > > What is the issue for the 3 ‘no image’ issue (marked red) in the report? > Do we have a solution now? > That's the preM3 Build. I am looking back in the AB, and I do not see the master failure for qemumips, we had a problem with PPC due to oprofile being broken, that has been fixed for M3rc1.
The P1022DS has been failing for a while, I think Matthew needs to give it some love to make it better. Sau! > Thanks! > > Song > > *From:*Palalau, AlexandruX > *Sent:* Thursday, January 24, 2013 7:23 AM > *To:* yocto@yoctoproject.org > *Cc:* Liu, Song > *Subject:* Fullpass Test Report for Yocto 1.4 20130115 Build > > Hello, > Here is the fullpass test report for Yocto 1.4 20130115 build. The > testings for qemuppc, mpc8315e, and p1022ds are blocked since the images > didn't build out due to some known issues (oprofile and libxml failures). > > We have some new bugs regarding CoreBuildSystem (Bug 3745. 3756, 3757). > Also, there are some problems regarding smart (Bug 3768, 3769). No > problems under qemu this time. > > Attached you can find the full test result. > > > > *Test Summary > -------------------------* > > *Test Result Summary* > > *Component* > > > > *Target* > > > > *Status* > > > > *Comments* > > *BSP* > > > > Beagleboard > > > > GOOD > > > > Everything runs well > > > > > > Routerstationpro > > > > GOOD > > > > Everything runs well > > > > > > Mpc8315e-rdb > > > > BLOCK > > > > No image built out > > > > P1022DS > > > > BLOCK > > > > No image built out > > *QEMU* > > > > qemuarm > > > > GOOD > > > > Everything runs well > > ** > > > > qemux86 > > > > GOOD > > > > Everything runs well > > ** > > > > qemux86-64 > > > > GOOD > > > > Everything runs well > > > > > > qemuppc > > > > GOOD > > > > Everything runs well > > > > > > qemumips > > > > BLOCK > > > > No image built out > > *Core Build System* > > > > BUGGY > > > > gtk-directfb image build failed; disk space monitoring gives error > ;Bitbake remake/remake-native check; Compile and load kernel; Crosstap > script check. > > *ADT Toolchain* > > > > BUGGY > > > > gtk+-2.0 missing from the userbuilt toolchain; autoreconf run failed > > *Compliance* > > > > Not running > > *Stress* > > > > Beagleboard > > > > Not running > > BLOCK > > > > Critical bugs, more than 50% test cases are blocked > > GOOD > > > > Only Normal, Minor or Enhancement bugs, less than 10% test cases failed > > BUGGY > > > > 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)* > > *Beagleboard Sato-SDK* > > > > 66 > > > > 0 > > > > 66 > > > > 0 > > > > 0 > > *Routerstationpro Sato-SDK* > > > > 43 > > > > 0 > > > > 43 > > > > 0 > > > > 0 > > *Mpc8315e-rdb Sato-SDK* > > > > 45 > > > > 0 > > > > 0 > > > > 0 > > > > 45 > > *P1022DS* > > > > 42 > > > > 0 > > > > 0 > > > > 0 > > > > 42 (bug 3476) > > *Qemux86* > > > > 82 > > > > 0 > > > > 82 > > > > 0 > > > > 0 > > *Qemux86-64* > > > > 82 > > > > 0 > > > > 82 > > > > 0 > > > > 0 > > *Qemuarm Sato* > > > > 42 > > > > 0 > > > > 42 > > > > 0 > > > > 0 > > *Qemuarm Sato-SDK* > > > > 47 > > > > 0 > > > > 47 > > > > 0 > > > > 0 > > *Qemumips Sato* > > > > 42 > > > > 0 > > > > 42 > > > > 0 > > > > 0 > > *Qemumips Sato-SDK* > > > > 47 > > > > 0 > > > > 47 > > > > 0 > > > > 0 > > *Qemuppc Sato* > > > > 42 > > > > 0 > > > > 0 > > > > 0 > > > > 42 > > *Qemuppc Sato-SDK* > > > > 47 > > > > 0 > > > > 0 > > > > 0 > > > > 47 > > *Core Build System* > > > > 78 > > > > 2 > > > > 72 > > > > 4 (bug 3523,3745, 3642) > > > > 2 > > *ADT Toolchain* > > > > 22 > > > > 0 > > > > 20 > > > > 2 (bug 3338, 3758) > > > > 0 > > *HOB* > > > > 38 > > > > 0 > > > > 37 > > > > 1(3001) > > > > 0 > > *Compliance* > > > > 2 > > > > 2 > > > > 0 > > > > 0 > > > > 0 > > *Stress* > > > > 2 > > > > 2 > > > > 0 > > > > 0 > > > > 0 > > *Total* > > > > 769 > > > > 6 > > > > 580 > > > > 7 > > > > 178 > > > * You can check the detailed test result in attachment for each target. > ** The failed/blocked case number is listed with failed cases’ bug number. > > > *Commit information > --------------------------------* > Location: http://autobuilder.yoctoproject.org/pub/nightly/20130115-2 > Tree/Branch: poky/master > Commit: 9eb88ceb39b7d0b8ddc6487e61ce8edadef10ec4 > > * > Issue Summary > -----------------------------------* > > *Component* > > > > *Bug Number* > > > > *Target Milestone* > > *System & Core OS* > > > > *System Usage* > > > > New! 3769 smart: some packages can not be reinstalled > New! 3768 smart: --yaml option doesn't work > > > > 1.4 > 1.4 > > *Others* > > > > Bug 3476 Autobuilder failing on fsl-ppc > > > > 1.4 M2 > > *Core Build System* > > > > Bug 3642 gtk-demo fails to run for gtk-directfb image > Bug 3523 Disk space monitoring gives error: Unknown event > New!Bug 3745 Bitbake remake/remake-native check fail > New!Bug 3757 Compile and load kernel fail > New!Bug 3756 Crosstap script fail > > > > 1.4 > 1.4 > 1.4 > 1.4 M3 > ---- > > *ADT Toolchain* > > > > Bug 3338 iptables-1.4.15: autoreconf run failed on gmae-toolchain > Bug 3758 Package gtk+-2.0 missing from the userbuilt toolchain > > > > 1.4 M2 > 1.4 M3 > > *Compliance* > > > > Not running > > > > *Stress* > > > > Not running > > > > > > > > *Verified Bugs > ----------------------------------- > *1. *[Bug 3643]* <http://bugzilla.pokylinux.org/show_bug.cgi?id=3643>: > smart config --help error: Invalid command 'config' > 2. *[Bug 3646]* <http://bugzilla.pokylinux.org/show_bug.cgi?id=3646>: > non GPLv3 build failure with core-image-basic > > > Br, > > Alexandru Palalau > > QA contractor Yocto Project > _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
