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

Bruce Ashfield bruce.ashfield at windriver.com
Tue Jul 10 05:50:59 PDT 2012


On 12-07-10 2:44 AM, Tom Zanussi wrote:
> On Mon, 2012-07-09 at 23:26 -0700, Saul Wold wrote:
>> On 07/09/2012 10:50 PM, Tom Zanussi wrote:
>>> On Mon, 2012-07-09 at 16:38 -0700, Saul Wold wrote:
>>>> On 07/09/2012 04:30 PM, elizabeth.flanagan at intel.com wrote:
>>>>>
>>>>>           Build status: FAILURE
>>>>>
>>>>> Buildslave for this Build: *ab05*
>>>>> Complete logs for all build steps:
>>>>> http://autobuilder.yoctoproject.org:8010/builders/nightly-mips/builds/487
>>>>> Build Reason: Triggerable(nightly-mips)
>>>>> Build Source Stamp: *[branch master]
>>>>> 90ad663909c0c8a405b22a510c9f957007d02669*
>>>>> /Detailed log of last build step:/
>>>>> http://autobuilder.yoctoproject.org:8010/builders/nightly-mips/builds/487/steps/shell_25/logs/stdio
>>>>>
>>>>>
>>>>>
>>>>>           Last 20 lines of "shell_25.stdio":
>>>>>
>>>>> NOTE: Running noexec task 7243 of 7288 (ID: 499,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/tasks/task-core-qt.bb,
>>>>> do_package_write)
>>>>> NOTE: package fotowall-0.9-r3: task do_package_write_deb: Succeeded
>>>>> NOTE: package fotowall-0.9-r3: task do_package_write_ipk: Succeeded
>>>>> NOTE: package fotowall-0.9-r3: task do_package_write_rpm: Succeeded
>>>>> NOTE: Running noexec task 7244 of 7288 (ID: 2469,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/qt-apps/fotowall_0.9.bb,
>>>>> do_package_write)
>>>>> NOTE: package qt4-x11-free-4.8.1-r44.1: task do_package_write_ipk: Succeeded
>>>>> NOTE: package qt4-x11-free-4.8.1-r44.1: task do_package_write_deb: Succeeded
>>>>> NOTE: package qt4-x11-free-4.8.1-r44.1: task do_package_write_rpm: Succeeded
>>>>> NOTE: Running noexec task 7245 of 7288 (ID: 4982,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/qt4/qt4-x11-free_4.8.1.bb,
>>>>> do_package_write)
>>>>> NOTE: Running noexec task 7246 of 7288 (ID: 4984,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/qt4/qt4-x11-free_4.8.1.bb,
>>>>> do_build)
>>>>> NOTE: Running noexec task 7247 of 7288 (ID: 2471,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/qt-apps/fotowall_0.9.bb,
>>>>> do_build)
>>>>> NOTE: Running noexec task 7248 of 7288 (ID: 2456,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/qt-apps/quicky_0.4.bb,
>>>>> do_build)
>>>>> NOTE: Running noexec task 7249 of 7288 (ID: 501,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/tasks/task-core-qt.bb,
>>>>> do_build)
>>>>> NOTE: Tasks Summary: Attempted 7249 tasks of which 2302 didn't need to
>>>>> be rerun and 2 failed.
>>>>>
>>>>> Summary: 2 tasks failed:
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-extended/libzypp/libzypp_git.bb,
>>>>> do_compile
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-kernel/perf/perf_3.4.bb,
>>>>> do_compile
>>>>> Summary: There were 22 WARNING messages shown.
>>>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>>>>
>>>>> /Detailed log of last build step:/
>>>>> http://autobuilder.yoctoproject.org:8010/builders/nightly-mips/builds/487/steps/shell_33/logs/stdio
>>>>>
>>>>>
>>>>>
>>>>>           Last 20 lines of "shell_33.stdio":
>>>>>
>>>>> | -w,w wide output n numeric WCHAN,UID -H process hierarchy
>>>>> | NOTE: Test Result for qemumips core-image-sato
>>>>> | NOTE: Testcase PASS FAIL NORESULT
>>>>> | NOTE: SSH 0 1 0
>>>>> | NOTE: SCP 0 1 0
>>>>> | NOTE: dmesg 0 1 0
>>>>> | NOTE: zypper_help 0 1 0
>>>>> | NOTE: zypper_search 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!!!
>>>>> NOTE: package core-image-sato-1.0-r0: task do_qemuimagetest_standalone:
>>>>> Failed
>>>>> ERROR: Task 0
>>>>> (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-sato/images/core-image-sato.bb,
>>>>> do_qemuimagetest_standalone) failed with exit code '1'
>>>>> NOTE: Tasks Summary: Attempted 183 tasks of which 182 didn't need to be
>>>>> rerun and 1 failed.
>>>>>
>>>>> Summary: 1 task failed:
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-sato/images/core-image-sato.bb,
>>>>> do_qemuimagetest_standalone
>>>>> 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-mips/builds/487/steps/shell_102/logs/stdio
>>>>>
>>>>>
>>>>>
>>>>>           Last 20 lines of "shell_102.stdio":
>>>>>
>>>>> NOTE: Running noexec task 7096 of 7118 (ID: 2873,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-qt/qt4/qt4-x11-free_4.8.1.bb,
>>>>> do_build)
>>>>> NOTE: Running noexec task 7097 of 7118 (ID: 364,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-extended/tasks/task-core-lsb.bb,
>>>>> do_build)
>>>>> NOTE: Running task 7098 of 7118 (ID: 52,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta-qt3/recipes-qt3/images/core-image-lsb-qt3.bb,
>>>>> do_rootfs)
>>>>> NOTE: Running task 7099 of 7118 (ID: 22,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-extended/images/core-image-lsb-dev.bb,
>>>>> do_rootfs)
>>>>> NOTE: Running task 7100 of 7118 (ID: 7,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-extended/images/core-image-lsb.bb,
>>>>> do_rootfs)
>>>>> NOTE: package core-image-lsb-qt3-1.0-r0: task do_rootfs: Started
>>>>> NOTE: package core-image-lsb-dev-1.0-r0: task do_rootfs: Started
>>>>> NOTE: package core-image-lsb-1.0-r0: task do_rootfs: Started
>>>>> NOTE: package core-image-lsb-qt3-1.0-r0: task do_rootfs: Succeeded
>>>>> NOTE: Running noexec task 7101 of 7118 (ID: 55,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta-qt3/recipes-qt3/images/core-image-lsb-qt3.bb,
>>>>> do_build)
>>>>> NOTE: package core-image-lsb-1.0-r0: task do_rootfs: Succeeded
>>>>> NOTE: Running noexec task 7102 of 7118 (ID: 10,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-extended/images/core-image-lsb.bb,
>>>>> do_build)
>>>>> NOTE: package core-image-lsb-dev-1.0-r0: task do_rootfs: Succeeded
>>>>> NOTE: Running noexec task 7103 of 7118 (ID: 25,
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-extended/images/core-image-lsb-dev.bb,
>>>>> do_build)
>>>>> NOTE: Tasks Summary: Attempted 7103 tasks of which 3826 didn't need to
>>>>> be rerun and 1 failed.
>>>>>
>>>>> Summary: 1 task failed:
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-kernel/perf/perf_3.4.bb,
>>>>> do_compile
>>>>
>>>> Perf failed and Tom I think is looking into it.
>>>>
>>>
>>> There seems to be a couple problems here.
>>>
>>> One is that we seem to now have the opposite problem with what's been
>>> pulled in for perf - before we had the recipe changes pulled in (to a
>>> testing branch) but not the kernel changes so it failed.
>>>
>>> Now we apparently have the kernel changes being used in the build since
>>> the SRCREVs were pulled in, but without the corresponding recipe patches
>>> since they haven't been pulled in.
>>>
>>> As mentioned before, one set won't work without the other.
>>>
>>> So basically what's happened here is that the kernel changes are causing
>>> this part of the scripting support to be built NO_LIBPYTHON has been
>>> removed and what it shows is an actual problem with mips vis a vis the
>>> _ABIN32 not defined error, which is I'm also seeing in my
>>> still-in-progress testing of the latest perf feature patchset.
>>>
>>> I'm still looking into it, and will patch this mips problem once I find
>>> a fix, but in the meantime, if you need to fix things up, you should
>>> just revert the SRCREV changes until you can pull in the perf recipe
>>> changes.
>>>
>>
>> I have to admit, I am really confused now, master, which this was built
>> from has a SRCREV from Bruce that claimed to have changed perf, but
>> later in the day admitted he forgot to update the perf bits.
>>
>> But now you are saying it has the perf bits, maybe only for mips, but
>> not the other ARCHs?
>>
>> Tom, Bruce, we really need to have a coordinated clean set, this is
>> causing a lot of pain right now.
>>
>
> There has always been only a 'coordinated clean set', which I posted
> together originally, but didn't spell out explicitly in v2, but did in
> v3.
>
> There were 2 sets of kernel patches, one for 3.2 and one for 3.4, which
> made up the kernel side of this change.  Along with that were the perf
> recipe changes that corresponded to those.
>
> So Bruce pulled in the kernel changes and sent you a SRCREV update to
> make those changes 'live'.  But they still needed to go 'live' with the
> corresponding perf recipe changes.
>
> Bruce forgot to send you the SRCREV update for the 3.2 changes, but did
> send the 3.4 changes.
>
> Those changes contain changes for all the arches, including mips.  It
> just so happens that perf doesn't compile on mips, and I'll need to
> submit yet another kernel patch to fix mips.  So far everything else
> works fine, but mips has a compile error.
>
> I think I now have a patch that will fix the mips compile error, and
> will submit that as a new patch for both 3.4 and 3.4, which will also
> need to be pulled in to the kernel (and Bruce will need to send new
> SRCREVs to cover that).  Once that's done, my latest perf recipe
> patchset can be pulled in and then everything should be fine.

Agreed.

Bruce

>
> Tom
>
>> Sau!
>>
>>> Tom
>>>
>>>> Sau!
>>>>
>>>>
>>>>> Summary: There were 27 WARNING messages shown.
>>>>> 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
>>>>>
>>>>
>>>
>>>
>>
>
>




More information about the yocto-builds mailing list