[Yocto-builds] buildbot failure in Yocto on cedartrail

Bruce Ashfield bruce.ashfield at windriver.com
Thu May 17 18:14:40 PDT 2012


On 12-05-17 8:28 PM, Tom Zanussi wrote:
> On Thu, 2012-05-17 at 17:23 -0700, Darren Hart wrote:
>> Beth, I'm thinking this looks like an infrastructure issue again. Thoughts?
>>
>> Tom are you aware of any issues here.
>>
>> This path does look a bit odd:
>> yocto/standard/cedartrail-standard.scc
>>
>
> I don't think this is the 0-length problem...
>
> But it does looks like a kernel-tools mismatch e.g. using the new kernel
> tools with an old kernel.

Nothing would have changed on the branches for this lately. What's
the configuration here ?

master ?

Bruce

>
> Tom
>
>> Bruce is that normal?
>>
>> --
>> Darren
>>
>>
>> ERROR: Function failed: do_patch (see
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.24038
>> for further information)
>> ERROR: Logfile of failure stored in:
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.24038
>> Log data follows:
>> | Branch meta-temp set up to track remote branch meta from origin.
>> | git reset --mixed 620917de59eeb934b9f8cf35cc2d95c1ac8ed0fc
>> | Deleted branch meta-temp (was 620917d).
>> |
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/sysroots/x86_64-linux/usr/bin/updateme:
>> line 434: yocto/standard/cedartrail-standard.scc: No such file or directory
>> |
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/sysroots/x86_64-linux/usr/bin/updateme:
>> line 436: yocto/standard/cedartrail-standard.scc: No such file or directory
>> |
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/sysroots/x86_64-linux/usr/bin/updateme:
>> line 437: yocto/standard/cedartrail-standard.scc: No such file or directory
>> |
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/sysroots/x86_64-linux/usr/bin/updateme:
>> line 438: yocto/standard/cedartrail-standard.scc: No such file or directory
>> |
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/sysroots/x86_64-linux/usr/bin/updateme:
>> line 441: yocto/standard/cedartrail-standard.scc: No such file or directory
>> | readlink: missing operand
>>
>> On 05/17/2012 01:08 PM, elizabeth.flanagan at intel.com wrote:
>>>
>>>          Build status: FAILURE
>>>
>>> Buildslave for this Build: *ab07*
>>> Complete logs for all build steps:
>>> http://autobuilder.yoctoproject.org:8010/builders/cedartrail/builds/92
>>> Build Reason: Triggerable(cedartrail)
>>> Build Source Stamp: *[branch master]
>>> d4e265661517f8dd4e1648fdc56bac5973f986f6*
>>> Blamelist:
>>>
>>> **
>>> Yocto Autobuilder Trivia/Challenge until May 1st
>>>
>>> -------------------------------------------------------------------
>>> Welcome to the Yocto Autobuilder Riddle
>>> The purpose of this challenge is to encourage people to read failure emails
>>> Please send all answers to elizabeth.flanagan at intel.com
>>> -------------------------------------------------------------------
>>> This one is simple. No fair if you already know it.
>>> Find the easter egg hidden in the yocto 1.1.1 release notes.
>>>
>>> Rules:
>>> 1. First person with the right answer wins.
>>> 2. Send me an email with the answer and the subject line: I know that
>>> answer!
>>> 3. Yes, there is a prize! With your submission please send a mail
>>> address! ** *- 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