[Yocto-builds] buildbot failure in Yocto on nightly-ppc

Mon Feb 4 02:08:47 PST 2013

Known issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=3717

Thanks,
Laurentiu

On 02/04/2013 07:53 AM, yocto-builds at yoctoproject.org wrote:
> 
>         Build status: FAILURE
> 
> Buildslave for this Build: *ab06*
> Complete logs for all build steps:
> http://autobuilder.yoctoproject.org:8010/builders/nightly-ppc/builds/784
> Build Reason: Triggerable(nightly-ppc)
> Build Source Stamp: *[branch master]
> 75f470cd18d693a9a96d9849291c2c8de4dcbeb8*
> /Detailed log of last build step:/
> http://autobuilder.yoctoproject.org:8010/builders/nightly-ppc/builds/784/steps/shell_29/logs/stdio
> 
> 
> 
>         Last 20 lines of "shell_29.stdio" Error log:
> 
> | from operf_counter.h:33,
> | from operf_utils.cpp:25:
> |
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/sysroots/qemuppc/usr/src/kernel/include/linux/types.h:13:2:
> warning: #warning "Attempt to use kernel headers from user space, see
> http://kernelnewbies.org/KernelHeaders" [-Wcpp]
> | operf_utils.cpp: In function 'bool _op_get_event_codes(std::vector*)':
> | operf_utils.cpp:151:21: error: 'pfm_initialize' was not declared in
> this scope
> | operf_utils.cpp:151:26: error: 'PFM_SUCCESS' was not declared in this
> scope
> | operf_utils.cpp:166:45: error: 'PFM_PLM3' was not declared in this scope
> | operf_utils.cpp:166:55: error: 'PFM_OS_NONE' was not declared in this
> scope
> | operf_utils.cpp:166:72: error: 'pfm_get_os_event_encoding' was not
> declared in this scope
> | operf_utils.cpp:167:14: error: 'PFM_SUCCESS' was not declared in this
> scope
> | make[2]: *** [operf_utils.o] Error 1
> | make[2]: *** Waiting for unfinished jobs....
> | make[2]: Leaving directory
> `/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/ppc603e-poky-linux/oprofile/0.9.8-r2.1/oprofile-0.9.8/libperf_events'
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory
> `/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/ppc603e-poky-linux/oprofile/0.9.8-r2.1/oprofile-0.9.8'
> | make: *** [all] Error 2
> | ERROR: oe_runmake failed
> | ERROR: Function failed: do_compile (see
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/ppc603e-poky-linux/oprofile/0.9.8-r2.1/temp/log.do_compile.29171
> for further information)
> ERROR: Task 2758
> (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/meta/recipes-kernel/oprofile/oprofile_0.9.8.bb,
> do_compile) failed with exit code '1'
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> /Detailed log of last build step:/
> http://autobuilder.yoctoproject.org:8010/builders/nightly-ppc/builds/784/steps/shell_39/logs/stdio
> 
> 
> 
>         Last 20 lines of "shell_39.stdio" Error log:
> 
> | -F extra full X registers --heading --no-heading --context
> | ********* misc options *********
> | -V,V show version L list format codes f ASCII art forest
> | -m,m,-L,-T,H threads S children in sum -y change -l format
> | -M,Z security data c true command name -c scheduling class
> | -w,w wide output n numeric WCHAN,UID -H process hierarchy
> | NOTE: Test Result for qemuppc core-image-sato
> | NOTE: Testcase PASS FAIL NORESULT
> | NOTE: SSH 0 1 0
> | NOTE: SCP 0 1 0
> | NOTE: dmesg 0 1 0
> | NOTE: smart_help 0 1 0
> | NOTE: smart_query 0 1 0
> | NOTE: rpm_query 0 1 0
> | NOTE: connman 0 1 0
> | NOTE: shutdown 0 1 0
> | DEBUG: Python function do_qemuimagetest_standalone finished
> | ERROR: Function failed: Some testcases fail, pls. check test result
> and test log!!!
> ERROR: Task 0
> (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/meta/recipes-sato/images/core-image-sato.bb,
> do_qemuimagetest_standalone) failed with exit code '1'
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> /Detailed log of last build step:/
> http://autobuilder.yoctoproject.org:8010/builders/nightly-ppc/builds/784/steps/shell_56/logs/stdio
> 
> 
> 
>         Last 20 lines of "shell_56.stdio" Error log:
> 
> | from operf_counter.h:33,
> | from operf_utils.cpp:25:
> |
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/sysroots/mpc8315e-rdb/usr/src/kernel/include/linux/types.h:13:2:
> warning: #warning "Attempt to use kernel headers from user space, see
> http://kernelnewbies.org/KernelHeaders" [-Wcpp]
> | operf_utils.cpp: In function 'bool _op_get_event_codes(std::vector*)':
> | operf_utils.cpp:151:21: error: 'pfm_initialize' was not declared in
> this scope
> | operf_utils.cpp:151:26: error: 'PFM_SUCCESS' was not declared in this
> scope
> | operf_utils.cpp:166:45: error: 'PFM_PLM3' was not declared in this scope
> | operf_utils.cpp:166:55: error: 'PFM_OS_NONE' was not declared in this
> scope
> | operf_utils.cpp:166:72: error: 'pfm_get_os_event_encoding' was not
> declared in this scope
> | operf_utils.cpp:167:14: error: 'PFM_SUCCESS' was not declared in this
> scope
> | make[2]: *** [operf_utils.o] Error 1
> | make[2]: *** Waiting for unfinished jobs....
> | make[2]: Leaving directory
> `/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/ppce300c3-poky-linux/oprofile/0.9.8-r2.1/oprofile-0.9.8/libperf_events'
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory
> `/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/ppce300c3-poky-linux/oprofile/0.9.8-r2.1/oprofile-0.9.8'
> | make: *** [all] Error 2
> | ERROR: oe_runmake failed
> | ERROR: Function failed: do_compile (see
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/build/tmp/work/ppce300c3-poky-linux/oprofile/0.9.8-r2.1/temp/log.do_compile.11643
> for further information)
> ERROR: Task 2667
> (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-ppc/build/meta/recipes-kernel/oprofile/oprofile_0.9.8.bb,
> do_compile) failed with exit code '1'
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> 
> 
> *-The Yocto BuildBot*
> 
> 
> _______________________________________________
> Yocto-builds mailing list
> Yocto-builds at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-builds
>