Yocto 1.7_M2 release candidate 1 ready for QA

Yocto 1.7_M2 release candidate 1 ready for QA

[Flanagan, Elizabeth]

Full green build!

http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1

bitbake 4aaf56bfbad4aa626be8a2f7a5f70834c3311dd3
eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37
eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904
meta-fsl-arm 6ef8db67df3436a463851ff95dcfb6a66132f3c0
meta-fsl-ppc 5efa2d27dcf4637b008faf782b5e257b748b24c0
meta-intel 67b7f6f3a03ddbdcf66823eb5a236edbc0aa4858
meta-minnow ee48eba5895178ec19febee2e0a2d8b0f3ace0e9
meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45
oecore 7986adeac16550b33f65fded39a55f668e0e543f
poky 2d1660112e54653f7bb763939d0416472c49fe01


-- 
Elizabeth Flanagan
Yocto Project
Build and Release

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[Georgescu, Alexandru C]

Ha, nice to see green here! :)
--
Alexandru Georgescu
Yocto QA Engineer
SSG/SSD Open Source Technology Center Romania




On 30/07/14 09:41, "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
wrote:

>Full green build!
>
>http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1
>
>bitbake 4aaf56bfbad4aa626be8a2f7a5f70834c3311dd3
>eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37
>eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904
>meta-fsl-arm 6ef8db67df3436a463851ff95dcfb6a66132f3c0
>meta-fsl-ppc 5efa2d27dcf4637b008faf782b5e257b748b24c0
>meta-intel 67b7f6f3a03ddbdcf66823eb5a236edbc0aa4858
>meta-minnow ee48eba5895178ec19febee2e0a2d8b0f3ace0e9
>meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45
>oecore 7986adeac16550b33f65fded39a55f668e0e543f
>poky 2d1660112e54653f7bb763939d0416472c49fe01
>
>
>-- 
>Elizabeth Flanagan
>Yocto Project
>Build and Release

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[João Henrique Ferreira de Freitas]

[-- Attachment #1: Type: text/plain, Size: 2981 bytes --]


Hi,

I've tested all toolchains available at 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/

My test program is very simple:

--- c.cpp ---
#include <limits>

int main() {}
---

Two considerations

1) the of ppce500v2-toolchain-1.6+snapshot.sh 
<http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/poky-eglibc-x86_64-core-image-sato-ppce500v2-toolchain-1.6+snapshot.sh> 
and armv7a-vfp-neon-toolchain-1.6+snapshot.sh 
<http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/poky-eglibc-x86_64-core-image-sato-armv7a-vfp-neon-toolchain-1.6+snapshot.sh> 
is less than others toolchains

2) when I try to compile c.cpp, using ppce500v2 or armv7a I get:

source /opt/poky/1.6+snapshot/environment-setup-ppce500v2-poky-linux-gnuspe
$CXX c.cpp

In file included from c.cpp:2:0:
/opt/poky/1.6+snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c++/4.9.0/limits:42:28: 
fatal error: bits/c++config.h: No such file or directory
  #include <bits/c++config.h>

I can't figure out what happened with these two toolchains.

# find /opt/poky/1.6+snapshot/ -name c++config.h
[sudo] password for joaohf:
/opt/poky/1.6+snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c++/4.9.0/powerpc-poky-linux-gnuspe/bits/c++config.h
/opt/poky/1.6+snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/src/debug/gcc-runtime/4.9.0-r0/gcc-4.9.0/build.powerpc-poky-linux-gnuspe.powerpc-poky-linux-gnuspe/powerpc-poky-linux-gnuspe/libstdc++-v3/include/powerpc-poky-linux-gnuspe/bits/c++config.h

Someone has any hint?

I suspect something at meta-fsl-ppc and meta-fsl-arm.


Is there QA tests against toolchains? I think there is nice to have one. 
Like installs all toolchain locally and use each one to compile something.


Thanks.



On 30-07-2014 03:52, Georgescu, Alexandru C wrote:
> Ha, nice to see green here! :)
> --
> Alexandru Georgescu
> Yocto QA Engineer
> SSG/SSD Open Source Technology Center Romania
>
>
>
>
> On 30/07/14 09:41, "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
> wrote:
>
>> Full green build!
>>
>> http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1
>>
>> bitbake 4aaf56bfbad4aa626be8a2f7a5f70834c3311dd3
>> eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37
>> eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904
>> meta-fsl-arm 6ef8db67df3436a463851ff95dcfb6a66132f3c0
>> meta-fsl-ppc 5efa2d27dcf4637b008faf782b5e257b748b24c0
>> meta-intel 67b7f6f3a03ddbdcf66823eb5a236edbc0aa4858
>> meta-minnow ee48eba5895178ec19febee2e0a2d8b0f3ace0e9
>> meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45
>> oecore 7986adeac16550b33f65fded39a55f668e0e543f
>> poky 2d1660112e54653f7bb763939d0416472c49fe01
>>
>>
>> -- 
>> Elizabeth Flanagan
>> Yocto Project
>> Build and Release

-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil


[-- Attachment #2: Type: text/html, Size: 4187 bytes --]

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[Richard Purdie]

On Fri, 2014-08-01 at 23:10 -0300, João Henrique Ferreira de Freitas
wrote:
> 
> Hi,
> 
> I've tested all toolchains available at
> http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/
> 
> My test program is very simple: 
> 
> --- c.cpp ---
> #include <limits>
> 
> int main() {}
> ---
> 
> Two considerations 
> 
> 1) the of ppce500v2-toolchain-1.6+snapshot.sh and
> armv7a-vfp-neon-toolchain-1.6+snapshot.sh is less than others
> toolchains
> 
> 2) when I try to compile c.cpp, using ppce500v2 or armv7a I get:
> 
> source /opt/poky/1.6
> +snapshot/environment-setup-ppce500v2-poky-linux-gnuspe
> $CXX c.cpp
> 
> In file included from c.cpp:2:0:
> /opt/poky/1.6
> +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c
> ++/4.9.0/limits:42:28: fatal error: bits/c++config.h: No such file or
> directory
>  #include <bits/c++config.h>
> 
> I can't figure out what happened with these two toolchains.
> 
> # find /opt/poky/1.6+snapshot/ -name c++config.h
> [sudo] password for joaohf: 
> /opt/poky/1.6
> +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c
> ++/4.9.0/powerpc-poky-linux-gnuspe/bits/c++config.h
> /opt/poky/1.6
> +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/src/debug/gcc-runtime/4.9.0-r0/gcc-4.9.0/build.powerpc-poky-linux-gnuspe.powerpc-poky-linux-gnuspe/powerpc-poky-linux-gnuspe/libstdc++-v3/include/powerpc-poky-linux-gnuspe/bits/c++config.h
> 
> Someone has any hint?
> 
> I suspect something at meta-fsl-ppc and meta-fsl-arm.
> 
> 
> Is there QA tests against toolchains? I think there is nice to have
> one. Like installs all toolchain locally and use each one to compile
> something.
> 

Just to let you know this email is useful thanks and there is something
being done about this. Alex is looking into why our testing hasn't shown
up the problem. If these are the meta-fsl toolchains, its likely our
test coverage doesn't extend to those and that is why the issue has been
missed. There is only so much testing we can do on a regular basis.

Ultimately we plan to automate the testing of the toolchains but that is
something we continue to work towards, its not ready yet.

On the specific errors, I think its likely the fact we're using one
compiler over multiple different configurations and there is likely some
kind of path issue somewhere. It may be worth filing bugs on these
issues to ensure they don't get lost.

Thanks again for pointing out the problem though, it is something that
needs to get fixed (and we need to improve the automated test coverage).

Cheers,

Richard

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[João Henrique Ferreira de Freitas]

On 05-08-2014 06:05, Richard Purdie wrote:
>
>
> On the specific errors, I think its likely the fact we're using one
> compiler over multiple different configurations and there is likely some
> kind of path issue somewhere. It may be worth filing bugs on these
> issues to ensure they don't get lost.

Ok, I will fill.

Thanks for the status update about it.


-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[João Henrique Ferreira de Freitas]

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]


On 05-08-2014 06:05, Richard Purdie wrote:
> On the specific errors, I think its likely the fact we're using one 
> compiler over multiple different configurations and there is likely 
> some kind of path issue somewhere. It may be worth filing bugs on 
> these issues to ensure they don't get lost. 

Bug filled, 6613
*
*

-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil


[-- Attachment #2: Type: text/html, Size: 841 bytes --]

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[Richard Purdie]

On Fri, 2014-08-01 at 23:10 -0300, João Henrique Ferreira de Freitas
wrote:
> 
> Hi,
> 
> I've tested all toolchains available at
> http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/
> 
> My test program is very simple: 
> 
> --- c.cpp ---
> #include <limits>
> 
> int main() {}
> ---
> 
> Two considerations 
> 
> 1) the of ppce500v2-toolchain-1.6+snapshot.sh and
> armv7a-vfp-neon-toolchain-1.6+snapshot.sh is less than others
> toolchains
> 
> 2) when I try to compile c.cpp, using ppce500v2 or armv7a I get:
> 
> source /opt/poky/1.6
> +snapshot/environment-setup-ppce500v2-poky-linux-gnuspe
> $CXX c.cpp
> 
> In file included from c.cpp:2:0:
> /opt/poky/1.6
> +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c
> ++/4.9.0/limits:42:28: fatal error: bits/c++config.h: No such file or
> directory
>  #include <bits/c++config.h>
> 
> I can't figure out what happened with these two toolchains.

You can fix the ppc toolchain with 
"ln -s powerpc-poky-linux-gnuspe sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c++/4.9.0/powerpc-poky-linux"

Cheers,

Richard

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[Richard Purdie]

On Tue, 2014-08-05 at 11:00 +0100, Richard Purdie wrote:
> On Fri, 2014-08-01 at 23:10 -0300, João Henrique Ferreira de Freitas
> wrote:
> > 
> > Hi,
> > 
> > I've tested all toolchains available at
> > http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/
> > 
> > My test program is very simple: 
> > 
> > --- c.cpp ---
> > #include <limits>
> > 
> > int main() {}
> > ---
> > 
> > Two considerations 
> > 
> > 1) the of ppce500v2-toolchain-1.6+snapshot.sh and
> > armv7a-vfp-neon-toolchain-1.6+snapshot.sh is less than others
> > toolchains
> > 
> > 2) when I try to compile c.cpp, using ppce500v2 or armv7a I get:
> > 
> > source /opt/poky/1.6
> > +snapshot/environment-setup-ppce500v2-poky-linux-gnuspe
> > $CXX c.cpp
> > 
> > In file included from c.cpp:2:0:
> > /opt/poky/1.6
> > +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c
> > ++/4.9.0/limits:42:28: fatal error: bits/c++config.h: No such file or
> > directory
> >  #include <bits/c++config.h>
> > 
> > I can't figure out what happened with these two toolchains.
> 
> You can fix the ppc toolchain with 
> "ln -s powerpc-poky-linux-gnuspe sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c++/4.9.0/powerpc-poky-linux"

I also couldn't reproduce this with the armv7 toolchain. Do you have the
logs from that failure?

Cheers,

Richard

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[João Henrique Ferreira de Freitas]

On 05-08-2014 07:32, Richard Purdie wrote:
> I also couldn't reproduce this with the armv7 toolchain. Do you have the
> logs from that failure?
>

You are right. I retest armv7 and there is no problem. I think I lost 
myself during install-test cycle

Thanks for your attention.

-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil

Re: Yocto 1.7_M2 release candidate 1 ready for QA

[Georgescu, Alexandru C]

Hi,
As RP mentioned in a previous mail, we aren¹t covering the meta-fsl
toolchain on our QA. We are validating though on the other platforms that
we cover and progressing with the automation in this area should validate
at least the basic functionality of the toolchain on the other platforms
as well.

Regards,
--
Alexandru Georgescu
Yocto QA Engineer
SSG/SSD Open Source Technology Center Romania




On 05/08/14 14:22, "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
wrote:

>
>On 05-08-2014 07:32, Richard Purdie wrote:
>> I also couldn't reproduce this with the armv7 toolchain. Do you have the
>> logs from that failure?
>>
>
>You are right. I retest armv7 and there is no problem. I think I lost
>myself during install-test cycle
>
>Thanks for your attention.
>
>-- 
>João Henrique Ferreira de Freitas - joaohf_at_gmail.com
>Campinas-SP-Brasil
>
>-- 
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto