+ Jeremy

On 12 November 2013 14:01, Tyler Baker <tyler.ba...@linaro.org> wrote:

> Hi All,
>
> It seems we have broken LDT with the documentation updates.
>
> Our install tests confirm this issue. Sometime on November 11th the LDT
> installation stopped working.
>
>
> http://validation.linaro.org/dashboard/filters/~tyler-baker/lava-master-installation-git-smart-http
>
> Any thoughts here?
>
> ---------- Forwarded message ----------
> From: DeBerg, Jeremy L <jeremy.deb...@intermec.com>
> Date: 12 November 2013 13:37
> Subject: lava-deployment-tool failing
> To: "tyler.ba...@linaro.org" <tyler.ba...@linaro.org>
>
>
>  Hey Tyler,
>
>
>
> The lava-deployment-tool is broken, I receive this error:
>
>
>
> > lava_scheduler_app:0019_set_testjob_owner
>
> > lava_scheduler_app:0020_auto__add_field_testjob__results_bundle
>
> > lava_scheduler_app:0021_rename_results_link
>
> >
> lava_scheduler_app:0022_auto__chg_field_testjob__results_bundle__add_unique_testjob__results_b
>
> > lava_scheduler_app:0023_auto__add_field_devicetype_use_celery
>
> > lava_scheduler_app:0024_auto__add_field_devicetype_display
>
> >
> lava_scheduler_app:0025_auto__chg_field_testjob__results_bundle__chg_field_testjob_submit_toke
>
> > lava_scheduler_app:0026_auto__add_field_device_device_version
>
> > lava_scheduler_app:0027_auto__add_field_testjob_priority
>
> > lava_scheduler_app:0028_auto__del_field_devicetype_use_celery
>
> >
> lava_scheduler_app:0029_auto__add_jobfailuretag__add_field_testjob_failure_comment
>
> >
> lava_scheduler_app:0030_auto__add_field_testjob_sub_id__add_field_testjob_target_group
>
> > lava_scheduler_app:0031_auto__add_field_testjob_multinode_definition
>
> > lava_scheduler_app:0032_auto__add_field_testjob_original_definition
>
> - Loading initial data for lava_scheduler_app.
>
> Installed 0 object(s) from 0 fixture(s)
>
> + set +x
>
> Starting instance again...
>
> + sudo start lava-instance LAVA_INSTANCE=production
>
> lava-instance (production) start/running
>
> + set +x
>
> INFO: building documentation for lava-android-test from
> /srv/lava/.cache/git-cache/exports/lava-android-test/2013-10-01-08f25ef/doc
>
> INFO: building documentation for lava-dispatcher from
> /srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-11-08-8a9833c/doc
>
> INFO: building documentation for lava-server from
> /srv/lava/.cache/git-cache/exports/lava-server/2013-10-17-97c7da5/doc
>
> INFO: building documentation for linaro-dashboard-bundle from
> /srv/lava/.cache/git-cache/exports/linaro-dashboard-bundle/2013-08-07-a8f2158/doc
>
> Running Sphinx v1.1.3
>
>
>
> Exception occurred:
>
>   File "/usr/lib/python2.7/dist-packages/sphinx/cmdline.py", line 188, in
> main
>
>     warningiserror, tags)
>
>   File "/usr/lib/python2.7/dist-packages/sphinx/application.py", line 102,
> in __init__
>
>     confoverrides or {}, self.tags)
>
>   File "/usr/lib/python2.7/dist-packages/sphinx/config.py", line 216, in
> __init__
>
>     exec code in config
>
>   File
> "/srv/lava/instances/production/var/www/lava-server/static/docs/_src/conf.py",
> line 53, in <module>
>
>     import lava_server
>
> ImportError: No module named lava_server
>
> The full traceback has been saved in /tmp/sphinx-err-1U0et6.log, if you
> want to report the issue to the developers.
>
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
>
> Either send bugs to the mailing list at <
> http://groups.google.com/group/sphinx-dev/>,
>
> or report them in the tracker at <
> http://bitbucket.org/birkenfeld/sphinx/issues/>. Thanks!
>
> Running installation step docs
>
> INFO: building documentation for lava-android-test from
> /srv/lava/.cache/git-cache/exports/lava-android-test/2013-10-01-08f25ef/doc
>
> INFO: building documentation for lava-dispatcher from
> /srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-11-08-8a9833c/doc
>
> INFO: building documentation for lava-server from
> /srv/lava/.cache/git-cache/exports/lava-server/2013-10-17-97c7da5/doc
>
> INFO: building documentation for linaro-dashboard-bundle from
> /srv/lava/.cache/git-cache/exports/linaro-dashboard-bundle/2013-08-07-a8f2158/doc
>
> Running Sphinx v1.1.3
>
>
>
> Exception occurred:
>
>   File "/usr/lib/python2.7/dist-packages/sphinx/cmdline.py", line 188, in
> main
>
>     warningiserror, tags)
>
>   File "/usr/lib/python2.7/dist-packages/sphinx/application.py", line 102,
> in __init__
>
>     confoverrides or {}, self.tags)
>
>   File "/usr/lib/python2.7/dist-packages/sphinx/config.py", line 216, in
> __init__
>
>     exec code in config
>
>   File
> "/srv/lava/instances/production/var/www/lava-server/static/docs/_src/conf.py",
> line 53, in <module>
>
>     import lava_server
>
> ImportError: No module named lava_server
>
> The full traceback has been saved in /tmp/sphinx-err-BWaJik.log, if you
> want to report the issue to the developers.
>
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
>
> Either send bugs to the mailing list at <
> http://groups.google.com/group/sphinx-dev/>,
>
> or report them in the tracker at <
> http://bitbucket.org/birkenfeld/sphinx/issues/>. Thanks!
>
> All installation is done
>
>
>
>
>
> Is this you guys or Sphinx?
>
>
>
> Thanks,
>
>
>
> -Jeremy
>
> This message is intended only for the named recipient. If you are not the 
> intended recipient, you are notified that disclosing, copying, distributing 
> or taking any action based on the contents of this information is strictly 
> prohibited.
>
>
>
>
>
> --
> Tyler Baker
> Technical Architect, LAVA
> Linaro.org | Open source software for ARM SoCs
> Follow Linaro: http://www.facebook.com/pages/Linaro
> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
>



-- 
Tyler Baker
Technical Architect, LAVA
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to