Re: [yocto] cannot build image using sstate

[Patrick Ohly]

On Thu, 2017-03-09 at 08:54 +0200, Mircea Gliga wrote:
> Long story short: I have problems building an image, in a clean build 
> directory, reusing the shared state cache and downloads from a previous 
> build.
> A file created in the do_deploy_append task is not created(restored) 
> anymore when building using a previous sstate.
> 
> And now the long description:
> In my custom layer, in a kernel recipe, linux-stable.bb, I have appended 
> some operations to the `deploy` task, one of them is creating an U-Boot 
> FIT image:
> 
> linux-stable.bb:
> do_deploy_append() {
> [...]
>  #this line creates the image_signed.fit file
>   mkimage  [...] image_signed.fit
> 
> [...]
> }

Are you writing image_signed.fit into the ${DEPLOYDIR} or
${DEPLOY_DIR_IMAGE}? When writing directly into ${DEPLOY_DIR_IMAGE}, you
bypass the mechanism which adds files to the sstate cache and then you
get exactly the problem you describe.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] hddimg 4GB limit?

[Takashi Matsuzawa]

Hello.

I found hddimg 4GB-1 bye restriction because it creates a file called 
rootfs.img which is copied into FAT.

That means rootfs.img size must be below FAT max file size...



From: Takashi Matsuzawa
Sent: Thursday, March 9, 2017 1:51 PM
To: yocto@yoctoproject.org
Subject: hddimg 4GB limit?


Hello, Yocto.


I have looked into hddimg file.

According to image-live.bbclass, it is hardcoded to maximum 4GB size.

But should not this more large?

hddimg is generated by mkdosfs -F 32 that means the filesystem capacity is 
larger than 4GB.


I just hit this limit when generating an image that exceeds 4GB size.


I think I am look into using hdddirect instead (hopefully it does not have this 
limit?),

but I also want to check if hddimg 4GB limitation has some practical reason 
(other than above image-live.bbclass checking).

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] cannot build image using sstate

[Mircea Gliga]

Long story short: I have problems building an image, in a clean build 
directory, reusing the shared state cache and downloads from a previous 
build.
A file created in the do_deploy_append task is not created(restored) 
anymore when building using a previous sstate.


And now the long description:
In my custom layer, in a kernel recipe, linux-stable.bb, I have appended 
some operations to the `deploy` task, one of them is creating an U-Boot 
FIT image:


linux-stable.bb:
do_deploy_append() {
[...]
#this line creates the image_signed.fit file
 mkimage  [...] image_signed.fit

[...]
}

Then in my image recipe, my-custom-image.bb, I'm creating an archive 
with some files, including the above created FIT image:


my-custom-image.bb:

LINUXIMAGE = "image_signed.fit"
do_makeArch() {
[...]
   tar --owner root --group root -C ${DEPLOY_DIR_IMAGE} -cvf 
${DEPLOY_DIR_IMAGE}/psf/${IMAGEFILE} -h ${LINUXIMAGE}

[...]
}

addtask do_makeArch after do_image_complete before do_build


Now, create a new build directory, set DL_DIR and SSTATE_DIR in local 
conf, start build:

# source oe-init-build-env build2
# bitbake my-custom-image
ERROR: my-custom-image-1.0-r0 do_makeArch: Function failed: do_makeArch
Log data follows:
| DEBUG: Executing shell function do_makeArch
| tar: image_signed.fit: Cannot stat: No such file or directory
| tar: Exiting with failure status due to previous errors

So the image build fails, because the image_signed.fit file is not present.
After some short time the build is started, in the deploy directory I 
see that the zimage is already there but the FIT image is missing ...


This is confirmed by the linux-stable.bb's logs: log.do_deploy_setscene. 
It lists all the files that are restored from the sstate cache, 
image_signed.fit

is not one of them:

DEBUG: Executing shell function sstate_unpack_package
deploy-linux-stable/
deploy-linux-stable/zImage-machine.bin
deploy-linux-stable/zImage--4.8.4+git0+a2b42342b2-r0.2-machine-20170308134915.bin
deploy-linux-stable/zImage-at91-machine.dtb
deploy-linux-stable/README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
deploy-linux-stable/zImage--4.8.4+git0+a2b42342b2-r0.2-at91-machine-20170308134915.dtb
deploy-linux-stable/modules-machine.tgz
deploy-linux-stable/modules--4.8.4+git0+a2b42342b2-r0.2-machine-20170308134915.tgz
deploy-linux-stable/zImage
deploy-linux-stable/zImage-initramfs-4.8.4+gitAUTOINC+a2b42342b2-r0-machine-20170308134915.bin
deploy-linux-stable/zImage-initramfs-machine.bin
DEBUG: Shell function sstate_unpack_package finished


Any hints, on how to add my custom generated files to the sstate ? Or 
what am I doing wrong here ?

Thanks

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Khem Raj]

On 17-03-09 00:01:12, Trevor Woerner wrote:
> On Wed 2017-03-08 @ 04:51:04 PM, Khem Raj wrote:
> > On 17-03-08 19:01:05, Tom Rini wrote:
> > > On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote:
> > > > On 17-03-08 18:28:21, Tom Rini wrote:
> > > > > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote:
> > > > > 
> > > > > > openembedded-core updated bintuils from 2.27 to 2.28 which causes 
> > > > > > u-boot to
> > > > > > fail to compile:
> > > > > > 
> > > > > > arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for 
> > > > > > program headers, try linking with -N
> > > > > > 
> > > > > > Building with -N does fix the issue, so this patch simply adds that 
> > > > > > flag to
> > > > > > the build so it succeeds.
> > > > > > 
> > > > > > This has been build-tested, as well as run-tested on the firefly.
> > > > > > 
> > > > > > Signed-off-by: Trevor Woerner 
> > > > > 
> > > > > Unless there's an immediate need I would ask holding off on this for a
> > > > > bit, I want to track down why this is happening.
> > > > 
> > > > perhaps linker map files from 2.27 and 2.28 binutils will help to
> > > > understand it
> > > 
> > > Nothing is standing out yet:
> > > https://lists.denx.de/pipermail/u-boot/2017-March/283278.html
> > > https://lists.denx.de/pipermail/u-boot/2017-March/283286.html
> > 
> > I see that .data.rel.ro are generated eventhough they are empty they
> > appear to be in final link this section will hold constant variables
> > that gcc sees and needs dynamic relocation, that probably is not
> > relevant to u-boot since its linked stand-alone
> > 
> > Can you try to do just the final link with 2.28 and all built with 2.27
> > and see if it still happens, want to rule out assembler
> 
> Okay.
> 
> Building with 2.28 (and letting it fail), then repeating the final link step
> with 2.27 succeeds!

OK thats good. Can you post the output of readelf -e on final good and bad 
binaries

> 
>   $ arm-oe-linux-gnueabi-ld.bfd -v
>   GNU ld (GNU Binutils) 2.27.0.20160806
> 
>   $ arm-oe-linux-gnueabi-ld.bfd   -pie  --gc-sections -Bstatic -Ttext 
> 0x -o u-boot \
> -T u-boot.lds arch/arm/cpu/armv7/start.o --start-group  
> arch/arm/cpu/built-in.o  \
> arch/arm/cpu/armv7/built-in.o  arch/arm/lib/built-in.o  
> arch/arm/mach-rockchip/built-in.o \
> board/firefly/firefly-rk3288/built-in.o  cmd/built-in.o  
> common/built-in.o  disk/built-in.o \
> drivers/built-in.o  drivers/dma/built-in.o  drivers/gpio/built-in.o  
> drivers/i2c/built-in.o  \
> drivers/mmc/built-in.o  drivers/mtd/built-in.o  
> drivers/mtd/onenand/built-in.o  \
> drivers/mtd/spi/built-in.o  drivers/net/built-in.o  
> drivers/net/phy/built-in.o  \
> drivers/pci/built-in.o  drivers/power/built-in.o  
> drivers/power/battery/built-in.o  \
> drivers/power/domain/built-in.o  drivers/power/fuel_gauge/built-in.o  
> drivers/power/mfd/built-in.o  \
> drivers/power/pmic/built-in.o  drivers/power/regulator/built-in.o  
> drivers/serial/built-in.o  \
> drivers/spi/built-in.o  drivers/usb/common/built-in.o  
> drivers/usb/dwc3/built-in.o  \
> drivers/usb/emul/built-in.o  drivers/usb/eth/built-in.o  
> drivers/usb/gadget/built-in.o  \
> drivers/usb/gadget/udc/built-in.o  drivers/usb/host/built-in.o  
> drivers/usb/musb-new/built-in.o  \
> drivers/usb/musb/built-in.o  drivers/usb/phy/built-in.o  
> drivers/usb/ulpi/built-in.o  fs/built-in.o  \
> lib/built-in.o  net/built-in.o  test/built-in.o  test/dm/built-in.o 
> --end-group \
> arch/arm/lib/eabi_compat.o  arch/arm/lib/lib.a -Map u-boot.map
>   $ echo $?
>   0
> 
> Looking at the top couple lines of a diff between the map files of a
> binutils-2.27 build and this frankenbuild (both with SPL, neither with -N)
> gives:
> 
>   --- 2.27-without-N/u-boot.map   2017-03-08 13:26:26.966147350 -0500
>   +++ build-with-2.28-link-with-2.27/u-boot.map   2017-03-08 
> 23:48:43.593173398 -0500
>   @@ -5442,7 +5442,7 @@
> .iplt  0x000301a40x0 
> arch/arm/cpu/armv7/start.o
>0x000301a4. = ALIGN (0x4)
>
>   -.rodata 0x000301a80x134dc
>   +.rodata 0x000301a80x134b8
> *(SORT(.rodata*))
> .rodata.efi_boot_services
>0x000301a8   0xc8 lib/built-in.o
>   @@ -5859,4836 +5859,4836 @@
> .rodata.cb_erase.str1.1
>0x00033745   0x60 
> drivers/usb/gadget/built-in.o
> .rodata.cb_getvar.str1.1
>   -0x000337a5   0xfc 
> drivers/usb/gadget/built-in.o
>   -0x10c (size before relaxing)
>   +0x000337a5   0xea 
> drivers/usb/gadget/built-in.o
>   + 0xfa 

[yocto] hddimg 4GB limit?

[Takashi Matsuzawa]

Hello, Yocto.


I have looked into hddimg file.

According to image-live.bbclass, it is hardcoded to maximum 4GB size.

But should not this more large?

hddimg is generated by mkdosfs -F 32 that means the filesystem capacity is 
larger than 4GB.


I just hit this limit when generating an image that exceeds 4GB size.


I think I am look into using hdddirect instead (hopefully it does not have this 
limit?),

but I also want to check if hddimg 4GB limitation has some practical reason 
(other than above image-live.bbclass checking).

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Trevor Woerner]

On Wed 2017-03-08 @ 04:51:04 PM, Khem Raj wrote:
> On 17-03-08 19:01:05, Tom Rini wrote:
> > On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote:
> > > On 17-03-08 18:28:21, Tom Rini wrote:
> > > > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote:
> > > > 
> > > > > openembedded-core updated bintuils from 2.27 to 2.28 which causes 
> > > > > u-boot to
> > > > > fail to compile:
> > > > > 
> > > > >   arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for 
> > > > > program headers, try linking with -N
> > > > > 
> > > > > Building with -N does fix the issue, so this patch simply adds that 
> > > > > flag to
> > > > > the build so it succeeds.
> > > > > 
> > > > > This has been build-tested, as well as run-tested on the firefly.
> > > > > 
> > > > > Signed-off-by: Trevor Woerner 
> > > > 
> > > > Unless there's an immediate need I would ask holding off on this for a
> > > > bit, I want to track down why this is happening.
> > > 
> > > perhaps linker map files from 2.27 and 2.28 binutils will help to
> > > understand it
> > 
> > Nothing is standing out yet:
> > https://lists.denx.de/pipermail/u-boot/2017-March/283278.html
> > https://lists.denx.de/pipermail/u-boot/2017-March/283286.html
> 
> I see that .data.rel.ro are generated eventhough they are empty they
> appear to be in final link this section will hold constant variables
> that gcc sees and needs dynamic relocation, that probably is not
> relevant to u-boot since its linked stand-alone
> 
> Can you try to do just the final link with 2.28 and all built with 2.27
> and see if it still happens, want to rule out assembler

Okay.

Building with 2.28 (and letting it fail), then repeating the final link step
with 2.27 succeeds!

$ arm-oe-linux-gnueabi-ld.bfd -v
GNU ld (GNU Binutils) 2.27.0.20160806

$ arm-oe-linux-gnueabi-ld.bfd   -pie  --gc-sections -Bstatic -Ttext 
0x -o u-boot \
  -T u-boot.lds arch/arm/cpu/armv7/start.o --start-group  
arch/arm/cpu/built-in.o  \
  arch/arm/cpu/armv7/built-in.o  arch/arm/lib/built-in.o  
arch/arm/mach-rockchip/built-in.o \
  board/firefly/firefly-rk3288/built-in.o  cmd/built-in.o  
common/built-in.o  disk/built-in.o \
  drivers/built-in.o  drivers/dma/built-in.o  drivers/gpio/built-in.o  
drivers/i2c/built-in.o  \
  drivers/mmc/built-in.o  drivers/mtd/built-in.o  
drivers/mtd/onenand/built-in.o  \
  drivers/mtd/spi/built-in.o  drivers/net/built-in.o  
drivers/net/phy/built-in.o  \
  drivers/pci/built-in.o  drivers/power/built-in.o  
drivers/power/battery/built-in.o  \
  drivers/power/domain/built-in.o  drivers/power/fuel_gauge/built-in.o  
drivers/power/mfd/built-in.o  \
  drivers/power/pmic/built-in.o  drivers/power/regulator/built-in.o  
drivers/serial/built-in.o  \
  drivers/spi/built-in.o  drivers/usb/common/built-in.o  
drivers/usb/dwc3/built-in.o  \
  drivers/usb/emul/built-in.o  drivers/usb/eth/built-in.o  
drivers/usb/gadget/built-in.o  \
  drivers/usb/gadget/udc/built-in.o  drivers/usb/host/built-in.o  
drivers/usb/musb-new/built-in.o  \
  drivers/usb/musb/built-in.o  drivers/usb/phy/built-in.o  
drivers/usb/ulpi/built-in.o  fs/built-in.o  \
  lib/built-in.o  net/built-in.o  test/built-in.o  test/dm/built-in.o 
--end-group \
  arch/arm/lib/eabi_compat.o  arch/arm/lib/lib.a -Map u-boot.map
$ echo $?
0

Looking at the top couple lines of a diff between the map files of a
binutils-2.27 build and this frankenbuild (both with SPL, neither with -N)
gives:

--- 2.27-without-N/u-boot.map   2017-03-08 13:26:26.966147350 -0500
+++ build-with-2.28-link-with-2.27/u-boot.map   2017-03-08 
23:48:43.593173398 -0500
@@ -5442,7 +5442,7 @@
  .iplt  0x000301a40x0 
arch/arm/cpu/armv7/start.o
 0x000301a4. = ALIGN (0x4)
 
-.rodata 0x000301a80x134dc
+.rodata 0x000301a80x134b8
  *(SORT(.rodata*))
  .rodata.efi_boot_services
 0x000301a8   0xc8 lib/built-in.o
@@ -5859,4836 +5859,4836 @@
  .rodata.cb_erase.str1.1
 0x00033745   0x60 
drivers/usb/gadget/built-in.o
  .rodata.cb_getvar.str1.1
-0x000337a5   0xfc 
drivers/usb/gadget/built-in.o
-0x10c (size before relaxing)
+0x000337a5   0xea 
drivers/usb/gadget/built-in.o
+ 0xfa (size before relaxing)
  .rodata.cb_oem.str1.1
-0x000338a1   0x4e 
drivers/usb/gadget/built-in.o
+0x0003388f   0x4e 
drivers/usb/gadget/built-in.o
 

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Trevor Woerner]

On Wed 2017-03-08 @ 06:28:21 PM, Tom Rini wrote:

Whoa! I didn't know I'd find you here :-) Bravo!

> Unless there's an immediate need I would ask holding off on this for a
> bit, I want to track down why this is happening.

No problem. I really just want people to know I've found a work-around, just
in case.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Khem Raj]

On 17-03-08 19:01:05, Tom Rini wrote:
> On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote:
> > On 17-03-08 18:28:21, Tom Rini wrote:
> > > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote:
> > > 
> > > > openembedded-core updated bintuils from 2.27 to 2.28 which causes 
> > > > u-boot to
> > > > fail to compile:
> > > > 
> > > > arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for 
> > > > program headers, try linking with -N
> > > > 
> > > > Building with -N does fix the issue, so this patch simply adds that 
> > > > flag to
> > > > the build so it succeeds.
> > > > 
> > > > This has been build-tested, as well as run-tested on the firefly.
> > > > 
> > > > Signed-off-by: Trevor Woerner 
> > > 
> > > Unless there's an immediate need I would ask holding off on this for a
> > > bit, I want to track down why this is happening.
> > 
> > perhaps linker map files from 2.27 and 2.28 binutils will help to
> > understand it
> 
> Nothing is standing out yet:
> https://lists.denx.de/pipermail/u-boot/2017-March/283278.html
> https://lists.denx.de/pipermail/u-boot/2017-March/283286.html

I see that .data.rel.ro are generated eventhough they are empty they
appear to be in final link this section will hold constant variables
that gcc sees and needs dynamic relocation, that probably is not
relevant to u-boot since its linked stand-alone

Can you try to do just the final link with 2.28 and all built with 2.27
and see if it still happens, want to rule out assembler

> 
> I'm asking Trevor to poke at something that would change where we link
> things at and perhaps there's a linker bug here (this platform says that
> we link U-Boot at 0x0).
> 
> -- 
> Tom
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/yoctoAB.conf

[Graydon, Tracy]

Update yoctoAB.conf to reflect what is currently used in production and
add nightly-musl and nightly-x32 builds to the configuration.

Signed-off-by: Graydon, Tracy 
---
 buildset-config.meta-intel/yoctoAB.conf | 11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/buildset-config.meta-intel/yoctoAB.conf 
b/buildset-config.meta-intel/yoctoAB.conf
index ad22a8a..7ad8cc7 100644
--- a/buildset-config.meta-intel/yoctoAB.conf
+++ b/buildset-config.meta-intel/yoctoAB.conf
@@ -1,7 +1,6 @@
 [BuildSets]
-order: ['nightly-meta-intel', 'nightly-meta-intel-world',
-'intel-corei7-64', 'intel-corei7-64-lsb',
-'intel-corei7-64-rt', 'intel-corei7-64-lsb-rt', 'intel-core2-32',
-'intel-core2-32-rt', 'intel-core2-32-lsb-rt',
-'intel-quark', 'nuc', 'nuc-lsb', 'sugarbay', 
-'sugarbay-lsb']
+order: ['nightly-meta-intel', 'nightly-meta-intel-world', 'nightly-musl',
+'nightly-x32', 'intel-corei7-64', 'intel-corei7-64-lsb', 
+'intel-corei7-64-rt', 'intel-corei7-64-lsb-rt', 'intel-core2-32', 
+'intel-core2-32-rt', 'intel-core2-32-lsb-rt', 'intel-quark', 
+'nuc', 'nuc-lsb', 'sugarbay', 'sugarbay-lsb']
-- 
2.7.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/nightly-meta-intel.conf

[Graydon, Tracy]

Add the new nightly-musl and nightly-x32 builds to nightly-meta-intel
build scheduler triggers.

Signed-off-by: Graydon, Tracy 
---
 buildset-config.meta-intel/nightly-meta-intel.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/buildset-config.meta-intel/nightly-meta-intel.conf 
b/buildset-config.meta-intel/nightly-meta-intel.conf
index 557bb67..081726e 100644
--- a/buildset-config.meta-intel/nightly-meta-intel.conf
+++ b/buildset-config.meta-intel/nightly-meta-intel.conf
@@ -1,5 +1,5 @@
 [nightly-meta-intel]
-builders: 'example-worker'
+builders: ['yocto-ab-master.ostc.intel.com', 'yocto-ab01.ostc.intel.com', 
'yocto-ab02.ostc.intel.com', 'yocto-ab03.ostc.intel.com', 
'yocto-ab04.ostc.intel.com']
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp', 
'yocto':'meta-yocto', 'poky':'meta-poky'},
@@ -19,7 +19,7 @@ props: [{'release_me':{'prop_type':'ChoiceStringParameter',
'name': 'release_me',
'label':' Generate a release?:'}},
 {'poky_name':{'prop_type':'ChoiceStringParameter',
-   'choices': ['', 'pyro', 'morty', 'krogoth', 'jethro', 
'fido','dizzy','daisy','dora','dylan','danny','denzil','edison','bernard'],
+   'choices': ['', 'pyro', 'morty', 'krogoth', 'jethro', 
'fido'],
'name': 'poky_name',
'label':' Name of the poky release.For further 
info on release names see https://wiki.yoctoproject.org/wiki/Releases;> Releases  '}},
 {'is_milestone':{'prop_type':'ChoiceStringParameter',
@@ -94,7 +94,7 @@ steps: [{'SetDest':{}},
  'intel-core2-32-lsb-rt':{}, 
'intel-core2-32-rt':{},
  'intel-corei7-64':{}, 'intel-corei7-64-lsb':{},
  'intel-corei7-64-lsb-rt':{}, 
'intel-corei7-64-rt':{}, 
- 'intel-quark':{},
+ 'intel-quark':{}, 'nightly-musl':{}, 
'nightly-x32':{},
  'jasperforest':{}, 'jasperforest-lsb':{},
  'sugarbay':{}, 'sugarbay-lsb':{},
  'nuc':{}, 'nuc-lsb':{}}, 'schedulerNames_nowait' 
: {'nightly-meta-intel-world':{,
-- 
2.7.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/nightly-x32.conf

[Graydon, Tracy]

Add nightly-x32 buildset with world build for meta-intel autobuilder.

Signed-off-by: Graydon, Tracy 
---
 buildset-config.meta-intel/nightly-x32.conf | 60 +
 1 file changed, 60 insertions(+)
 create mode 100644 buildset-config.meta-intel/nightly-x32.conf

diff --git a/buildset-config.meta-intel/nightly-x32.conf 
b/buildset-config.meta-intel/nightly-x32.conf
new file mode 100644
index 000..cba4f00
--- /dev/null
+++ b/buildset-config.meta-intel/nightly-x32.conf
@@ -0,0 +1,60 @@
+[nightly-x32]
+builders: ['yocto-ab-master.ostc.intel.com', 'yocto-ab01.ostc.intel.com', 
'yocto-ab02.ostc.intel.com', 'yocto-ab03.ostc.intel.com', 
'yocto-ab04.ostc.intel.com']
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp', 
'yocto':'meta-yocto', 'poky':'meta-poky'},
+ 'branch':'master'}},
+{'meta-intel':
+{'repourl':'git://git.yoctoproject.org/meta-intel',
+ 'layerversion':{'intel':'meta-intel'},
+ 'branch':'master'}}]
+props: [{'kmeta':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'kmeta',
+   'default': '',
+   'label':' branch for KMETA_${MACHINE} (default 
is blank):'}},
+{'srcrev_meta':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'srcrev_meta',
+   'default': '${AUTOREV}',
+   'label':' SRCREV for KMETA_${MACHINE} (default 
is ${AUTOREV}):'}},
+{'srcuri_meta':{'prop_type':'StringParameter',
+   'size': 50,
+   'name': 'srcuri_meta',
+   'default': '',
+   'label':' SRC_URI_pn-linux-yocto KMETA append. 
(default is blank). This should be constructed as *just* the git uri 
portion of the   string. 
(git://git.yoctoproject.org/linux-yocto-3.19.git'}},
+{'kbranch':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'kbranch',
+   'default': '',
+   'label':' branch for KBRANCH_${MACHINE} 
(default is blank):'}},
+{'srcrev_machine':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'srcrev_machine',
+   'default': '${AUTOREV}',
+   'label':' SRCREV for KBRANCH. (default is 
${AUTOREV}):'}},
+{'srcuri_machine':{'prop_type':'StringParameter',
+   'size': 50,
+   'name': 'srcuri_machine',
+   'default': '',
+   'label':' SRC_URI_pn-linux-yocto KBRANCH 
append. (default is blank). This should be constructed as *just* the git 
uri portion of thestring. 
(git://git.yoctoproject.org/linux-yocto-3.19.git'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'GetBitbakeVersion': {}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64',
+'buildhistory' : False, 'x32': True,
+'distro': 'poky'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'PublishLayerTarballs':{}},
+{'BuildImages': {'images': 'core-image-minimal core-image-sato 
world'}},
+{'RunSanityTests': {'images': 'core-image-minimal'}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64',
+'buildhistory' : False, 'x32': True,
+'distro': 'poky'}},
+{'RunSanityTests': {'images': 'core-image-sato', 'suitesappend' : 
'x32lib'}},
+{'DownloadErrorReports': {}},
+{'SendErrorReport': {}},
+{'UploadToasterEventlog': {}},
+{'PublishArtifacts': {'artifacts': ['md5sums']}}]
-- 
2.7.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/nightly-musl.conf

[Graydon, Tracy]

Add nightly-musl buildset for meta-intel autobuilder.

Signed-off-by: Graydon, Tracy 
---
 buildset-config.meta-intel/nightly-musl.conf | 52 
 1 file changed, 52 insertions(+)
 create mode 100644 buildset-config.meta-intel/nightly-musl.conf

diff --git a/buildset-config.meta-intel/nightly-musl.conf 
b/buildset-config.meta-intel/nightly-musl.conf
new file mode 100644
index 000..02f7126
--- /dev/null
+++ b/buildset-config.meta-intel/nightly-musl.conf
@@ -0,0 +1,52 @@
+[nightly-musl]
+builders: ['yocto-ab-master.ostc.intel.com', 'yocto-ab01.ostc.intel.com', 
'yocto-ab02.ostc.intel.com', 'yocto-ab03.ostc.intel.com', 
'yocto-ab04.ostc.intel.com']
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp', 
'yocto':'meta-yocto', 'poky':'meta-poky'},
+ 'branch':'master'}},
+{'meta-intel':
+{'repourl':'git://git.yoctoproject.org/meta-intel',
+ 'layerversion':{'intel':'meta-intel'},
+ 'branch':'master'}}]
+props: [{'kmeta':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'kmeta',
+   'default': '',
+   'label':' branch for KMETA_${MACHINE} (default 
is blank):'}},
+{'srcrev_meta':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'srcrev_meta',
+   'default': '${AUTOREV}',
+   'label':' SRCREV for KMETA_${MACHINE} (default 
is ${AUTOREV}):'}},
+{'srcuri_meta':{'prop_type':'StringParameter',
+   'size': 50,
+   'name': 'srcuri_meta',
+   'default': '',
+   'label':' SRC_URI_pn-linux-yocto KMETA append. 
(default is blank). This should be constructed as *just* the git uri 
portion of the string. 
(git://git.yoctoproject.org/linux-yocto-3.19.git'}},
+{'kbranch':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'kbranch',
+   'default': '',
+   'label':' branch for KBRANCH_${MACHINE} 
(default is blank):'}},
+{'srcrev_machine':{'prop_type':'StringParameter',
+   'size': 15,
+   'name': 'srcrev_machine',
+   'default': '${AUTOREV}',
+   'label':' SRCREV for KBRANCH. (default is 
${AUTOREV}):'}},
+{'srcuri_machine':{'prop_type':'StringParameter',
+   'size': 50,
+   'name': 'srcuri_machine',
+   'default': '',
+   'label':' SRC_URI_pn-linux-yocto KBRANCH 
append. (default is blank). This should be constructed as *just* the git 
uri portion of the string. 
(git://git.yoctoproject.org/linux-yocto-3.19.git'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
+'buildhistory' : False, 'distro': 'poky',
+'atextappend' : '\nTCLIBC="musl"\n' }},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'BuildImages': {'images':  'core-image-minimal 
core-image-full-cmdline core-image-sato world'}},
+{'RunSanityTests': {'images': 'core-image-minimal 
core-image-full-cmdline core-image-sato'}},
+{'DownloadErrorReports': {}},
+{'SendErrorReport': {}}]
-- 
2.7.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Tom Rini]

On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote:
> On 17-03-08 18:28:21, Tom Rini wrote:
> > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote:
> > 
> > > openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot 
> > > to
> > > fail to compile:
> > > 
> > >   arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program 
> > > headers, try linking with -N
> > > 
> > > Building with -N does fix the issue, so this patch simply adds that flag 
> > > to
> > > the build so it succeeds.
> > > 
> > > This has been build-tested, as well as run-tested on the firefly.
> > > 
> > > Signed-off-by: Trevor Woerner 
> > 
> > Unless there's an immediate need I would ask holding off on this for a
> > bit, I want to track down why this is happening.
> 
> perhaps linker map files from 2.27 and 2.28 binutils will help to
> understand it

Nothing is standing out yet:
https://lists.denx.de/pipermail/u-boot/2017-March/283278.html
https://lists.denx.de/pipermail/u-boot/2017-March/283286.html

I'm asking Trevor to poke at something that would change where we link
things at and perhaps there's a linker bug here (this platform says that
we link U-Boot at 0x0).

-- 
Tom
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Khem Raj]

On 17-03-08 18:28:21, Tom Rini wrote:
> On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote:
> 
> > openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot to
> > fail to compile:
> > 
> > arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program 
> > headers, try linking with -N
> > 
> > Building with -N does fix the issue, so this patch simply adds that flag to
> > the build so it succeeds.
> > 
> > This has been build-tested, as well as run-tested on the firefly.
> > 
> > Signed-off-by: Trevor Woerner 
> 
> Unless there's an immediate need I would ask holding off on this for a
> bit, I want to track down why this is happening.

perhaps linker map files from 2.27 and 2.28 binutils will help to
understand it

> 
> -- 
> Tom
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Tom Rini]

On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote:

> openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot to
> fail to compile:
> 
>   arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program 
> headers, try linking with -N
> 
> Building with -N does fix the issue, so this patch simply adds that flag to
> the build so it succeeds.
> 
> This has been build-tested, as well as run-tested on the firefly.
> 
> Signed-off-by: Trevor Woerner 

Unless there's an immediate need I would ask holding off on this for a
bit, I want to track down why this is happening.

-- 
Tom
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [qa-tools][PATCH v2] testopia_update: Improvements on update action functionality

[jose . perez . carranza]

From: Jose Perez Carranza 

Some improvements were applied when using option
action=create :

   - Create a new option to update test runs by ID
   - Create functions to load results and update test run
   - Add warning to use –testrun-id
   - Improvements to update_test_run using exiting data of test run
   - Create function get test run details by ID
   - Create Dummy product to use on cases when specific product is not
 relevant

Signed-off-by: Jose Perez Carranza 
---
 testopia_update.py  | 60 +
 testopia_update/product/__init__.py | 17 +--
 2 files changed, 61 insertions(+), 16 deletions(-)

diff --git a/testopia_update.py b/testopia_update.py
index 044074a..50c3325 100755
--- a/testopia_update.py
+++ b/testopia_update.py
@@ -17,6 +17,29 @@ ACTIONS = ('create', 'update')
 BRANCHES = ('master', 'jethro', 'dizzy', 'daisy', 'noexists')
 CATEGORIES = ('AUTO', 'MANUAL')
 
+
+def update_test_run(env, build, test_run, results):
+missing = product.update_test_run(test_run, results)
+for tcid in missing:
+logger.warn("%s: Test run %d, Case %d wasn't updated" %
+(sys.argv[0], test_run['run_id'], tcid))
+
+
+def load_results(results_log):
+if not results_log:
+logger.error("%s: For action update --results-log needs to be 
specified"
+ % (sys.argv[0]))
+sys.exit(1)
+if not os.path.exists(args.results_log):
+logger.error("%s: Results log (%s) doesn't exists."
+ % (sys.argv[0], results_log))
+sys.exit(1)
+
+res = product.parse_results_log(args.results_log)
+
+return res
+
+
 def load_opts(args, opts_list, opts):
 for to in opts_list:
 if to in vars(args):
@@ -26,6 +49,9 @@ def load_opts(args, opts_list, opts):
 if not hasattr(opts, to):
 logger.error("%s: Requires testopia %s in arguments or config." % \
 (sys.argv[0], to))
+if args.action == "update":
+logger.warn('for action create you can use only --testrun-id ' 
+
+'and --results-log if test run was already 
created')
 sys.exit(1)
 
 class Options(object):
@@ -73,6 +99,9 @@ def get_args():
 parser.add_argument('--test-plan', required=False,
 dest="plan_name", help='Name of the test plan of the product, used 
when \
 test plan name is different from product 
name.')
+parser.add_argument('--testrun-id', required=False,
+dest="trun_id", help='Number of the test run to be updated, this \
+  option should be used along with update action.')
 
 parser.add_argument('--results-log', required=False,
 dest="results_log", help='Results log.')
@@ -131,6 +160,21 @@ if __name__ == '__main__':
 print("%s\n" % p.name)
 sys.exit(0)
 
+if args.action == 'update' and args.trun_id:
+args.product_name = 'Dummy'
+product = get_product_class(args.product_name, products)
+try:
+tr = product.get_existing_test_run(int(args.trun_id))
+except Exception as e:
+logger.error("%s: Problem found with Test Run %s: \n==>%s"
+ % (sys.argv[0], args.trun_id, e))
+sys.exit(1)
+
+results = load_results(args.results_log)
+update_test_run(tr['environment_id'], tr['build_id'], tr, results)
+
+sys.exit(0)
+
 load_opts(args, testopia_opts, opts)
 
 params = ['action', 'product_name', 'branch_name', 'env_name']
@@ -205,16 +249,8 @@ if __name__ == '__main__':
 " and ID (%s)." % (sys.argv[0], template_test_run['run_id'],
 test_run['summary'], test_run['run_id']))
 elif args.action == "update":
-if not args.results_log:
-logger.error("%s: For update --results-log needs to be specified." 
\
-% (sys.argv[0]))
-sys.exit(1)
-if not os.path.exists(args.results_log):
-logger.error("%s: Results log (%s) don't exists." \
-% (sys.argv[0], args.results_log))
-sys.exit(1)
+results = load_results(args.results_log)
 
-results = product.parse_results_log(args.results_log)
 test_run = product.get_test_run(test_plan, env, build, 
args.project_date,
 args.project_version, args.category_name, args.optional)
 if not test_run:
@@ -224,8 +260,6 @@ if __name__ == '__main__':
 args.optional))
 sys.exit(1)
 
-missing = product.update_test_run(env, build, test_run, results)
-for tcid in missing:
-logger.warn("%s: Product %s, Test run %d, Case %d wasn't updated" 
%\
-(sys.argv[0], args.product_name, test_run['run_id'], tcid))
+update_test_run(env, build, test_run, 

Re: [yocto] [qa-tools][PATCH] testopia_update: Improvements on update action functionality

[Aníbal Limón]

On 03/08/2017 09:56 AM, jose.perez.carra...@linux.intel.com wrote:
> From: Jose Perez Carranza 
> 
> Some improvements were applied when using option
> action=create :
> 
>- Create a new option to update test runs by ID
>- Create functions to load results and check missing test cases
>- Add warning to use –testrun-id
>- Improvements to update_test_run using exiting data of test run
>- Create function get test run details by ID
>- Create Dummy product to use on cases when specific product is not
>  relevant
> 
> Signed-off-by: Jose Perez Carranza 
> ---
>  testopia_update.py  | 60 
> +
>  testopia_update/product/__init__.py | 17 +--
>  2 files changed, 61 insertions(+), 16 deletions(-)
> 
> diff --git a/testopia_update.py b/testopia_update.py
> index 044074a..9cd9ad1 100755
> --- a/testopia_update.py
> +++ b/testopia_update.py
> @@ -17,6 +17,29 @@ ACTIONS = ('create', 'update')
>  BRANCHES = ('master', 'jethro', 'dizzy', 'daisy', 'noexists')
>  CATEGORIES = ('AUTO', 'MANUAL')
>  
> +
> +def check_missing_tc(env, build, test_run, results):
> +missing = product.update_test_run(test_run, results)
> +for tcid in missing:
> +logger.warn("%s: Test run %d, Case %d wasn't updated" %
> +(sys.argv[0], test_run['run_id'], tcid))

Only one comment, change the check_missing_tc to something like
update_test_run because the first time i read the function name, i
thought that do other thing.

alimon

> +
> +
> +def load_results(results_log):
> +if not results_log:
> +logger.error("%s: For action update --results-log needs to be 
> specified"
> + % (sys.argv[0]))
> +sys.exit(1)
> +if not os.path.exists(args.results_log):
> +logger.error("%s: Results log (%s) doesn't exists."
> + % (sys.argv[0], results_log))
> +sys.exit(1)
> +
> +res = product.parse_results_log(args.results_log)
> +
> +return res
> +
> +
>  def load_opts(args, opts_list, opts):
>  for to in opts_list:
>  if to in vars(args):
> @@ -26,6 +49,9 @@ def load_opts(args, opts_list, opts):
>  if not hasattr(opts, to):
>  logger.error("%s: Requires testopia %s in arguments or config." 
> % \
>  (sys.argv[0], to))
> +if args.action == "update":
> +logger.warn('for action create you can use only --testrun-id 
> ' +
> +'and --results-log if test run was already 
> created')
>  sys.exit(1)
>  
>  class Options(object):
> @@ -73,6 +99,9 @@ def get_args():
>  parser.add_argument('--test-plan', required=False,
>  dest="plan_name", help='Name of the test plan of the product, used 
> when \
>  test plan name is different from product 
> name.')
> +parser.add_argument('--testrun-id', required=False,
> +dest="trun_id", help='Number of the test run to be updated, this \
> +  option should be used along with update 
> action.')
>  
>  parser.add_argument('--results-log', required=False,
>  dest="results_log", help='Results log.')
> @@ -131,6 +160,21 @@ if __name__ == '__main__':
>  print("%s\n" % p.name)
>  sys.exit(0)
>  
> +if args.action == 'update' and args.trun_id:
> +args.product_name = 'Dummy'
> +product = get_product_class(args.product_name, products)
> +try:
> +tr = product.get_existing_test_run(int(args.trun_id))
> +except Exception as e:
> +logger.error("%s: Problem found with Test Run %s: \n==>%s"
> + % (sys.argv[0], args.trun_id, e))
> +sys.exit(1)
> +
> +results = load_results(args.results_log)
> +check_missing_tc(tr['environment_id'], tr['build_id'], tr, results)
> +
> +sys.exit(0)
> +
>  load_opts(args, testopia_opts, opts)
>  
>  params = ['action', 'product_name', 'branch_name', 'env_name']
> @@ -205,16 +249,8 @@ if __name__ == '__main__':
>  " and ID (%s)." % (sys.argv[0], template_test_run['run_id'],
>  test_run['summary'], test_run['run_id']))
>  elif args.action == "update":
> -if not args.results_log:
> -logger.error("%s: For update --results-log needs to be 
> specified." \
> -% (sys.argv[0]))
> -sys.exit(1)
> -if not os.path.exists(args.results_log):
> -logger.error("%s: Results log (%s) don't exists." \
> -% (sys.argv[0], args.results_log))
> -sys.exit(1)
> +results = load_results(args.results_log)
>  
> -results = product.parse_results_log(args.results_log)
>  test_run = product.get_test_run(test_plan, env, build, 
> args.project_date,
>  

[yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

[Trevor Woerner]

openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot to
fail to compile:

arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program 
headers, try linking with -N

Building with -N does fix the issue, so this patch simply adds that flag to
the build so it succeeds.

This has been build-tested, as well as run-tested on the firefly.

Signed-off-by: Trevor Woerner 
---
 recipes-bsp/u-boot/files/binutils-2.28-ld-fix.patch | 13 +
 recipes-bsp/u-boot/u-boot-rockchip_git.bb   |  5 -
 2 files changed, 17 insertions(+), 1 deletion(-)
 create mode 100644 recipes-bsp/u-boot/files/binutils-2.28-ld-fix.patch

diff --git a/recipes-bsp/u-boot/files/binutils-2.28-ld-fix.patch 
b/recipes-bsp/u-boot/files/binutils-2.28-ld-fix.patch
new file mode 100644
index 000..9dfc463
--- /dev/null
+++ b/recipes-bsp/u-boot/files/binutils-2.28-ld-fix.patch
@@ -0,0 +1,13 @@
+Index: git/arch/arm/config.mk
+===
+--- git.orig/arch/arm/config.mk
 git/arch/arm/config.mk
+@@ -89,7 +89,7 @@ PLATFORM_LIBS := arch/arm/lib/eabi_compa
+ endif
+ 
+ # needed for relocation
+-LDFLAGS_u-boot += -pie
++LDFLAGS_u-boot += -N -pie
+ 
+ #
+ # FIXME: binutils versions < 2.22 have a bug in the assembler where
diff --git a/recipes-bsp/u-boot/u-boot-rockchip_git.bb 
b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
index 3b4f109..4887d5d 100644
--- a/recipes-bsp/u-boot/u-boot-rockchip_git.bb
+++ b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
@@ -9,7 +9,10 @@ LICENSE = "GPLv2+"
 LIC_FILES_CHKSUM = 
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
 COMPATIBLE_MACHINE = "(firefly-rk3288)"
 
-SRC_URI = "git://github.com/rockchip-linux/u-boot.git;branch=release;"
+SRC_URI = " \
+   git://github.com/rockchip-linux/u-boot.git;branch=release; \
+   file://binutils-2.28-ld-fix.patch \
+   "
 SRCREV = "${AUTOREV}"
 S = "${WORKDIR}/git"
 
-- 
2.12.0.rc1.48.g076c053

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Burton, Ross]

On 8 March 2017 at 17:24, Dominig ar Foll (Intel Open Source) <
dominig.arf...@fridu.net> wrote:

> as now the recipe is called because I have declared that I wanted to use
> vaapi.
> It seems to call fo gst-plugins-bad.
>
> There is obviously quite a few problem with that recipe.
>

gstreamer1.0-plugins-bad comes in 1.10.4 and +git_1.8.2 forms, the 1.10.4
version is preferred.  Your distro must have explicitly selected the +git
form.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Dominig ar Foll (Intel Open Source)]

  
  
Ross,
  
  as now the recipe is called because I have declared that I wanted
  to use vaapi.
  It seems to call fo gst-plugins-bad.
  
  There is obviously quite a few problem with that recipe.
  
  Regards.
  
  Dominig

Le 08/03/2017 à 16:38, Burton, Ross a
  écrit :


  

  On 8 March 2017 at 15:10, Dominig Ar
Foll 
wrote:
yes, I now that I build the latest.
I am checking in advance of phase what will break in
Automotive Grade Linux (AGL) when 2.3 is coming out of
the wood.
  
  
  
  When 2.3 is released it won't be using the git gst-plugins-bad
  recipe by default either.  I'll fix the recipe, but the git
  recipes are prone to breakage as they're not that tested.


(this is why I want to remove them)


Ross
  


-- 
Dominig ar Foll
Senior Software Architect
Intel Open Source Technology Centre
  

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Raspberry Pi2 Fails to boot into LXDE.

[Khem Raj]

On 17-03-08 12:40:51, Steve Plant wrote:
> Hi All,
> 
> 
> Very new to all this linux world, and especially Yocto.
> 
> 
> I'm working on a embedded project at the moment using a raspberry pi2 board.
> 
> 
> I have used toaster with Morty 2.2 to compile an image 
> using"rpi-basic-image", to this I have added the following bitbake variables:
> 
> Bitbake variables
> 
> DISTRO
> poky
> DL_DIR
> /home/steve/poky/downloads
> IMAGE_FSTYPES
> ext3 jffs2 tar.bz2 rpi-sdimg
> IMAGE_INSTALL_append
> packagegroup-core-x11-base packagegroup-lxde-base connman
> PACKAGE_CLASSES
> package_rpm
> SSTATE_DIR
> /home/steve/poky/sstate-cache
> 
> DISABLE_OVERSCAN
> 1
> GPU_MEM_1024
> 512
> 
> I have dd'ed the image to an SD card increased the sdb2 partition to the max 
> size and powered up the rpi. Everything looks fine to start with, as it 
> displays the four raspberrys in the top left, then the white "Yocto Project" 
> splash screen complete with small blue dot to the side appears, the progress 
> bar moves across to 100 percent, then the screen turns black with a white 
> cursor in the middle and it appears to freeze with only a very dim one second 
> flash of the "act" led.
> 
> 
> I have then connected the 7" touchscreen and apart from the added 
> multicolored square at the very beginning I get the exact same boot up 
> problem, hangs on the black screen with white cursor (good to see its all 
> resized correctly for the TfT through!!)
> 
> 
> Before adding the packagegroup-core-x11-base and packagegroup-lxde-base I 
> successfully copied over and ran the rpi-basic-image with no problem, ending 
> up with a usable console.
> 
> 
> Looking for any help here, I'm thinking I've missed adding a package, or some 
> type of local.conf instruction. any suggestions would be 
> appreciated.

Can you send the content of /var/log/Xorg.log file ?

> 
> 
> 
> Regards, Steve.

> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Khem Raj]

On 17-03-08 15:44:08, Burton, Ross wrote:
> On 8 March 2017 at 15:38, Burton, Ross  wrote:
> 
> > When 2.3 is released it won't be using the git gst-plugins-bad recipe by
> > default either.  I'll fix the recipe, but the git recipes are prone to
> > breakage as they're not that tested.
> >
> 
> In fact the git recipes are actually older than the default tarball
> releases...

I think git recipes should be removed, they are good for development
purposes and gst devs can overlay them locally if needed

> 
> Ross

> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [qa-tools][PATCH] scripts: Wrapper that helps to create a full test cycle

[jose . perez . carranza]

From: Jose Perez Carranza 

Add a wrapper that  helps to create the required test runs
for a full cycle on master branch.

Signed-off-by: Jose Perez Carranza 
---
 scripts/full-test-cycle-wrapper.sh | 302 +
 1 file changed, 302 insertions(+)
 create mode 100755 scripts/full-test-cycle-wrapper.sh

diff --git a/scripts/full-test-cycle-wrapper.sh 
b/scripts/full-test-cycle-wrapper.sh
new file mode 100755
index 000..f52cd96
--- /dev/null
+++ b/scripts/full-test-cycle-wrapper.sh
@@ -0,0 +1,302 @@
+#!/bin/bash
+#
+# Full Test Cycle wrapper
+#
+# Copyright (c) 2017, Intel Corporation.
+#
+# This program is free software; you can redistribute it and/or modify it
+# under the terms and conditions of the GNU General Public License,
+# version 2, as published by the Free Software Foundation.
+#
+# This program is distributed in the hope it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
+# more details.
+#
+#
+# This script is wrapper to create a set of test runs on testo[pia
+# for a full QA execution cycle.
+
+
+#Set variables to be used globally
+export CONFIG_FILE='testopia_update.config'
+export ACTION='create'
+export ENVIRONMETS=""
+export EXECUTION_TYPE=""
+export OPTIONAL=""
+export TEST_PLAN=""
+export IMAGE="core-image-sato-sdk_"
+
+#Go to the main directory of qa-tools
+FILEDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
+QADIR="`echo $FILEDIR | sed 's/scripts//g'`"
+cd $QADIR
+
+
+display_bars(){
+   if [ $1 == "START"  ]; then
+   echo "|### CREATING TEST RUNS FOR  - $2 - |"
+   elif [ $1 == "END"  ]; then
+echo "|--- TEST RUNS COMPLETED FOR - $2 - -"
+   fi
+}
+
+
+#Function that creates the Test Runs for specific component
+create_test_run(){
+   #Check if optional parameters are given
+   if [ -z $2  ]; then
+  OPT=""
+   else
+  OPT="-o $2"
+   fi
+
+   #echo " CREATING TEST RUNS FOR - $1 - #"
+   for ENV in "${ENVIRONMETS[@]}"
+   do
+ if [[ $2 == "BSP-MAN"  ]]; then
+ OPT="-o $IMAGE$ENV"
+ fi
+ for EXTP in $EXECUTION_TYPE
+ do
+#call the script that creates Test Runs
+./testopia_update.py --config $CONFIG_FILE -a $ACTION -p "${1}" -c 
$EXTP -b $BRANCH \
+-e "$ENV"  --project-version $VERSION --project-milestone "$VERSION 
$MILESTONE" \
+--project-date $PJDATE --project-revision $RELEASE-$REVISION $OPT 
$TEST_PLAN --verbose
+ done
+   done
+   #echo " TEST RUNS COMPLETED FOR - $1 - #"
+   #echo "."
+
+}
+
+create_yocto(){
+   #BSP MANUALS
+   ENVIRONMETS=("Genericx86_MMAX32" "Genericx86-64_NUC" "Beaglebone-Black" 
"EdgeRouter" "MPC8315e-rdb")
+   EXECUTION_TYPE="MANUAL"
+   create_test_run "${1}" "BSP-MAN"
+
+   #QEMUs Manuals
+   ENVIRONMETS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" "qemumips64" 
"qemuppc" "qemux86-64")
+   EXECUTION_TYPE="MANUAL"
+   create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
+
+   #QEMUs Autos
+   EVIRONMETS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" "qemumips64" 
"qemuppc" "qemux86-64" "qemux86-lsb" "qemux86_64-lsb")
+   ECUTION_TYPE="AUTO"
+   create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
+
+   #QEMUs Autos LSB
+   ENVIRONMETS=("qemux86-lsb" "qemux86_64-lsb")
+   EXECUTION_TYPE="AUTO"
+   create_test_run "${1}" "core-image-lsb-sdk_ANYQEMU"
+
+   #BSP Autos
+   ENVIRONMETS=("genericx86 - on MMAX32bit" "genericx86-64 on MMAX64" 
"genericx86-64 on NUC" "genericx86-64-WIC on MMAX64" \
+"genericx86-64-WIC on NUC" "genericx86-WIC on MMAX32"  
"MPC8315e-rdb" "Beaglebone Black" "EdgeRouter")
+   EXECUTION_TYPE="AUTO"
+   create_test_run "${1}" "core-image-sato-sdk_ANYBSP"
+
+   #BSP Autos
+   ENVIRONMETS=("genericx86-64-lsb on NUC" "genericx86-64-lsb on MMAX64" 
"genericx86-lsb on MMAX32bit")
+   EXECUTION_TYPE="AUTO"
+   create_test_run "${1}" "core-image-lsb-sdk_ANYBSP"
+
+}
+
+create_meta-intel(){
+   #BSP MANUALS
+   ENVIRONMETS=("core2-32_MMAX32" "corei7-64_NUC")
+   EXECUTION_TYPE="MANUAL"
+   create_test_run "${1}" "BSP-MAN"
+
+   #BSP Autos
+   ENVIRONMETS=("core2-32_MMAX32" "corei7-64_NUC" "corei7-64_MMAX64" 
"corei7-64_Joule" \
+"core2-32_WIC_MMAX32" "corei7-64_WIC_NUC" 
"corei7-64_WIC_MMAX64" "corei7-64_WIC_Joule" \
+   "intel-quark_Galileo" "intel-quark_WIC_Galileo")
+
+   EXECUTION_TYPE="AUTO"
+   create_test_run "${1}" "core-image-sato-sdk_ANYBSP"
+
+   #BSP Autos LSB
+   ENVIRONMETS=("core2-32_lsb_MMAX32" "corei7-64_lsb_NUC" 
"corei7-64_lsb_MMAX64" "corei7-64_lsb_Joule")
+
+   EXECUTION_TYPE="AUTO"
+   create_test_run "${1}" "core-image-lsb-sdk_ANYBSP"
+}
+
+
+#Function that set the environments and execution per component

[yocto] [qa-tools][PATCH] testopia_update: Improvements on update action functionality

[jose . perez . carranza]

From: Jose Perez Carranza 

Some improvements were applied when using option
action=create :

   - Create a new option to update test runs by ID
   - Create functions to load results and check missing test cases
   - Add warning to use –testrun-id
   - Improvements to update_test_run using exiting data of test run
   - Create function get test run details by ID
   - Create Dummy product to use on cases when specific product is not
 relevant

Signed-off-by: Jose Perez Carranza 
---
 testopia_update.py  | 60 +
 testopia_update/product/__init__.py | 17 +--
 2 files changed, 61 insertions(+), 16 deletions(-)

diff --git a/testopia_update.py b/testopia_update.py
index 044074a..9cd9ad1 100755
--- a/testopia_update.py
+++ b/testopia_update.py
@@ -17,6 +17,29 @@ ACTIONS = ('create', 'update')
 BRANCHES = ('master', 'jethro', 'dizzy', 'daisy', 'noexists')
 CATEGORIES = ('AUTO', 'MANUAL')
 
+
+def check_missing_tc(env, build, test_run, results):
+missing = product.update_test_run(test_run, results)
+for tcid in missing:
+logger.warn("%s: Test run %d, Case %d wasn't updated" %
+(sys.argv[0], test_run['run_id'], tcid))
+
+
+def load_results(results_log):
+if not results_log:
+logger.error("%s: For action update --results-log needs to be 
specified"
+ % (sys.argv[0]))
+sys.exit(1)
+if not os.path.exists(args.results_log):
+logger.error("%s: Results log (%s) doesn't exists."
+ % (sys.argv[0], results_log))
+sys.exit(1)
+
+res = product.parse_results_log(args.results_log)
+
+return res
+
+
 def load_opts(args, opts_list, opts):
 for to in opts_list:
 if to in vars(args):
@@ -26,6 +49,9 @@ def load_opts(args, opts_list, opts):
 if not hasattr(opts, to):
 logger.error("%s: Requires testopia %s in arguments or config." % \
 (sys.argv[0], to))
+if args.action == "update":
+logger.warn('for action create you can use only --testrun-id ' 
+
+'and --results-log if test run was already 
created')
 sys.exit(1)
 
 class Options(object):
@@ -73,6 +99,9 @@ def get_args():
 parser.add_argument('--test-plan', required=False,
 dest="plan_name", help='Name of the test plan of the product, used 
when \
 test plan name is different from product 
name.')
+parser.add_argument('--testrun-id', required=False,
+dest="trun_id", help='Number of the test run to be updated, this \
+  option should be used along with update action.')
 
 parser.add_argument('--results-log', required=False,
 dest="results_log", help='Results log.')
@@ -131,6 +160,21 @@ if __name__ == '__main__':
 print("%s\n" % p.name)
 sys.exit(0)
 
+if args.action == 'update' and args.trun_id:
+args.product_name = 'Dummy'
+product = get_product_class(args.product_name, products)
+try:
+tr = product.get_existing_test_run(int(args.trun_id))
+except Exception as e:
+logger.error("%s: Problem found with Test Run %s: \n==>%s"
+ % (sys.argv[0], args.trun_id, e))
+sys.exit(1)
+
+results = load_results(args.results_log)
+check_missing_tc(tr['environment_id'], tr['build_id'], tr, results)
+
+sys.exit(0)
+
 load_opts(args, testopia_opts, opts)
 
 params = ['action', 'product_name', 'branch_name', 'env_name']
@@ -205,16 +249,8 @@ if __name__ == '__main__':
 " and ID (%s)." % (sys.argv[0], template_test_run['run_id'],
 test_run['summary'], test_run['run_id']))
 elif args.action == "update":
-if not args.results_log:
-logger.error("%s: For update --results-log needs to be specified." 
\
-% (sys.argv[0]))
-sys.exit(1)
-if not os.path.exists(args.results_log):
-logger.error("%s: Results log (%s) don't exists." \
-% (sys.argv[0], args.results_log))
-sys.exit(1)
+results = load_results(args.results_log)
 
-results = product.parse_results_log(args.results_log)
 test_run = product.get_test_run(test_plan, env, build, 
args.project_date,
 args.project_version, args.category_name, args.optional)
 if not test_run:
@@ -224,8 +260,6 @@ if __name__ == '__main__':
 args.optional))
 sys.exit(1)
 
-missing = product.update_test_run(env, build, test_run, results)
-for tcid in missing:
-logger.warn("%s: Product %s, Test run %d, Case %d wasn't updated" 
%\
-(sys.argv[0], args.product_name, test_run['run_id'], tcid))
+check_missing_tc(env, 

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Burton, Ross]

On 8 March 2017 at 15:10, Dominig Ar Foll  wrote:

> yes, I now that I build the latest.
> I am checking in advance of phase what will break in Automotive Grade
> Linux (AGL) when 2.3 is coming out of the wood.
>

When 2.3 is released it won't be using the git gst-plugins-bad recipe by
default either.  I'll fix the recipe, but the git recipes are prone to
breakage as they're not that tested.

(this is why I want to remove them)

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Burton, Ross]

On 8 March 2017 at 15:38, Burton, Ross  wrote:

> When 2.3 is released it won't be using the git gst-plugins-bad recipe by
> default either.  I'll fix the recipe, but the git recipes are prone to
> breakage as they're not that tested.
>

In fact the git recipes are actually older than the default tarball
releases...

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Dominig Ar Foll]

 Ross,

yes, I now that I build the latest.
I am checking in advance of phase what will break in Automotive Grade Linux
(AGL) when 2.3 is coming out of the wood.

By the side, I also wants a 4.10 kernel for some test on virtualisation.

Regards.

Dominig
Le 08/03/2017 à 15:33, Burton, Ross a écrit :


On 8 March 2017 at 14:29, Dominig ar Foll (Intel Open Source) <
dominig.arf...@fridu.net> wrote:

> ERROR: Task 
> (/home/dominig/AGL/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_git.bb:do_patch)
>  failed with exit code '1'
>
> Are you aware that you're building the _git recipe and not the release?
Ross

-- 
Dominig ar Foll
Senior Software Architect
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Burton, Ross]

On 8 March 2017 at 14:29, Dominig ar Foll (Intel Open Source) <
dominig.arf...@fridu.net> wrote:

> ERROR: Task 
> (/home/dominig/AGL/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_git.bb:do_patch)
>  failed with exit code '1'
>
> Are you aware that you're building the _git recipe and not the release?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

[Dominig ar Foll (Intel Open Source)]

  
  
For info.
  as the target file of this patch
  (gst-plugins-bad-1.10.2/sys/decklink/gstdecklink.cpp) has changed,
  the patch now fails when building yocto/maser
  
  It was created with gst-plugins-bad-1.10.2 but poky now download
  1.10.4
  
  the patch can be found here :
poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/ensure-valid-sentinels-for-gst_structure_get-etc.patch
-- 
Dominig ar Foll
Senior Software Architect
Intel Open Source Technology Centre

-- error log --

ERROR: gstreamer1.0-plugins-bad-1.8.2+gitAUTOINC+5e73b5a484-r0 do_patch: Command Error: 'quilt --quiltrc /home/dominig/build/tmp/work/corei7-64-agl-linux/gstreamer1.0-plugins-bad/1.8.2+gitAUTOINC+5e73b5a484-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0  Output:
Applying patch ensure-valid-sentinels-for-gst_structure_get-etc.patch
patching file sys/decklink/gstdecklink.cpp
Hunk #1 FAILED at 476.
Hunk #2 FAILED at 489.
2 out of 2 hunks FAILED -- rejects in file sys/decklink/gstdecklink.cpp
patching file sys/decklink/gstdecklinkaudiosrc.cpp
Hunk #1 succeeded at 313 (offset -9 lines).
patching file sys/decklink/gstdecklinkvideosink.cpp
Hunk #1 succeeded at 158 (offset -5 lines).
Patch ensure-valid-sentinels-for-gst_structure_get-etc.patch does not apply (enforce with -f)
ERROR: gstreamer1.0-plugins-bad-1.8.2+gitAUTOINC+5e73b5a484-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/dominig/build/tmp/work/corei7-64-agl-linux/gstreamer1.0-plugins-bad/1.8.2+gitAUTOINC+5e73b5a484-r0/temp/log.do_patch.5672
ERROR: Task (/home/dominig/AGL/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_git.bb:do_patch) failed with exit code '1'


  

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Raspberry Pi2 Fails to boot into LXDE.

[Steve Plant]

Hi All,


Very new to all this linux world, and especially Yocto.


I'm working on a embedded project at the moment using a raspberry pi2 board.


I have used toaster with Morty 2.2 to compile an image using"rpi-basic-image", 
to this I have added the following bitbake variables:

Bitbake variables

DISTRO
poky
DL_DIR
/home/steve/poky/downloads
IMAGE_FSTYPES
ext3 jffs2 tar.bz2 rpi-sdimg
IMAGE_INSTALL_append
packagegroup-core-x11-base packagegroup-lxde-base connman
PACKAGE_CLASSES
package_rpm
SSTATE_DIR
/home/steve/poky/sstate-cache

DISABLE_OVERSCAN
1
GPU_MEM_1024
512

I have dd'ed the image to an SD card increased the sdb2 partition to the max 
size and powered up the rpi. Everything looks fine to start with, as it 
displays the four raspberrys in the top left, then the white "Yocto Project" 
splash screen complete with small blue dot to the side appears, the progress 
bar moves across to 100 percent, then the screen turns black with a white 
cursor in the middle and it appears to freeze with only a very dim one second 
flash of the "act" led.


I have then connected the 7" touchscreen and apart from the added multicolored 
square at the very beginning I get the exact same boot up problem, hangs on the 
black screen with white cursor (good to see its all resized correctly for the 
TfT through!!)


Before adding the packagegroup-core-x11-base and packagegroup-lxde-base I 
successfully copied over and ran the rpi-basic-image with no problem, ending up 
with a usable console.


Looking for any help here, I'm thinking I've missed adding a package, or some 
type of local.conf instruction. any suggestions would be 
appreciated.



Regards, Steve.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] why is VOLATILE_LOG_DIR mentioned in ref manual when it doesn't exist?

[Robert P. J. Day]

  not sure if i'm misreading this, but i note that an addition was
made to the ref manual back in dec 2016:

commit 5d2bdf49e569e44d02602501d72418f04dbe6e4a
Author: Scott Rifenbark 
Date:   Fri Dec 30 10:20:28 2016 -0800

ref-manual: New VOLATILE_LOG_DIR variable description

Fixes [YOCTO #6132]

No mention of how to make the target directory /var/log
persistent.  I added a note to the "post-install-logging"
image feature that points to the new VOLATILE_LOG_DIR
variable description, which I added to the glossary.

Signed-off-by: Scott Rifenbark 

diff --git a/documentation/ref-manual/ref-features.xml
b/documentation/ref-manual/ref-features.xml
index 282a517..a4516a2 100644
--- a/documentation/ref-manual/ref-features.xml
+++ b/documentation/ref-manual/ref-features.xml
@@ -297,6 +297,12 @@
 Enables logging postinstall script runs to
 the /var/log/postinstall.log file
 on first boot of the image on the target system.
+
+To make the /var/log directory
+on the target persistent, use the
+VOLATILE_LOG_DIR
+variable by setting it to "no".
+
 
 ptest-pkgs:
 Installs ptest packages for all ptest-enabled recipes.


but that is a broken link, and i see no definition or usage of that
variable. can someone clarify what is happening here?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto