[Yocto-builds] buildbot failure in Yocto on nightly-non-gpl3

[Saul Wold]

On 10/03/2012 02:19 PM, yocto-builds at yoctoproject.org wrote:
>
>         Build status: FAILURE
>
> Buildslave for this Build: *ab10.i.yoctoproject.org*
> Complete logs for all build steps:
> http://autobuilder.yoctoproject.org:8010/builders/nightly-non-gpl3/builds/309
>
> Build Reason: Triggerable(nightly-non-gpl3)
> Build Source Stamp: *[branch danny]
> 86c9aa8081f107420cd3763d0566d779daddc2b1*
>
>
> *-The Yocto BuildBot*
>
>
> _______________________________________________
> Yocto-builds mailing list
> Yocto-builds at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-builds
>

Additional info:
> NOTE: Tasks Summary: Attempted 63 tasks of which 63 didn't need to be rerun and all succeeded.
> Traceback (most recent call last):
>   File "/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-non-gpl3/build/bitbake/bin/bitbake", line 272, in <module>
>     ret = main()
>   File "/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-non-gpl3/build/bitbake/bin/bitbake", line 261, in main
>     return server.launchUI(ui_main, server_connection.connection, server_connection.events)
>   File "/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-non-gpl3/build/bitbake/lib/bb/server/process.py", line 269, in launchUI
>     return bb.cooker.server_main(self.cooker, uifunc, *args)
>   File "/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-non-gpl3/build/bitbake/lib/bb/cooker.py", line 1415, in server_main
>     ret = func(*args)
>   File "/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-non-gpl3/build/bitbake/lib/bb/ui/knotty.py", line 247, in main
>     elif not cmdline['action']:
> TypeError: string indices must be integers, not str
> mkdir: cannot create directory `/../../var/pseudo': Permission denied
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-non-gpl3/build/scripts/bitbake: line 178: /pseudo: No such file or directory
> program finished with exit code 127
> elapsedTime=191.376266

Not sure what happened here, this seems to be OK when I tried it 
directly on the machine and it started correctly.

Beth is there anything else on the command line or Environment when you 
start this?

Sau!