Good morning everyone,
I am getting in touch with you in order to show you an issue i am facing after submitting a basic Test Job Definition through my LAVA web page (localhost). I am a new LAVA user.
After submitting my job, I see the following error in the job's page :
Something seems to be going wrong with "commands" and I am trying to figure out what it is.
Did anyone already encountered this error in the past?
(I edited a jinja2 device type file and a jinja2 dictionary file as well to match my device's properties. The device type file is saved in /etc/lava-server/dispatcher-config/device-types/ and the device dictionary file is saved in /etc/lava-server/dispatcher-config/devices/).
Thank you for your help,
On 21 February 2018 at 16:53, Conrad Djedjebi conrad.djedjebi@linaro.org wrote:
Good morning everyone,
I am getting in touch with you in order to show you an issue i am facing after submitting a basic Test Job Definition through my LAVA web page (localhost). I am a new LAVA user.
What version of LAVA are you running? Integrating your own device is not easy, you should always be on the latest version - 2018.2-1 which is available from the LAVA repositories, as per the documentation.
After submitting my job, I see the following error in the job's page :
Something seems to be going wrong with "commands" and I am trying to figure out what it is.
This is old code. Current versions of that file do not even have that many lines: https://git.linaro.org/lava/lava-dispatcher.git/tree/lava_dispatcher/actions...
Did anyone already encountered this error in the past?
(I edited a jinja2 device type file and a jinja2 dictionary file as well to match my device's properties. The device type file is saved in /etc/lava-server/dispatcher-config/device-types/ and the device dictionary file is saved in /etc/lava-server/dispatcher-config/devices/).
An error in those changes is the most likely cause.
https://validation.linaro.org/static/docs/v2/device-integration.html
Thank you for your help,
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Good evening,
Thank you for your answer,
I was running the version 2016.12 of LAVA. I did a simple install on my Debian Stretch Desktop but Debian stable releases of LAVA do not receive updates to LAVA directly.
Today I installed lava-server from stretch-backports. I was expecting to get the 2018.2.1 version of LAVA as we can see here https://tracker.debian.org/pkg/lava-server, but the update I got was lava-server 2017.7.1 and lava-dispatcher 2017.7.1.
Do you know why a sudo apt -t stretch-backports install lava-server is not pointing to the 2018.2.1 version of lava-server and lava-dispatcher?
I added " deb http://deb.debian.org/debian stretch-backports main " to my /etc/apt/sources.list.
Best regards,
On 22 February 2018 at 16:11, Neil Williams neil.williams@linaro.org wrote:
On 21 February 2018 at 16:53, Conrad Djedjebi conrad.djedjebi@linaro.org wrote:
Good morning everyone,
I am getting in touch with you in order to show you an issue i am facing after submitting a basic Test Job Definition through my LAVA web page (localhost). I am a new LAVA user.
What version of LAVA are you running? Integrating your own device is not easy, you should always be on the latest version - 2018.2-1 which is available from the LAVA repositories, as per the documentation.
After submitting my job, I see the following error in the job's page :
Something seems to be going wrong with "commands" and I am trying to figure out what it is.
This is old code. Current versions of that file do not even have that many lines: https://git.linaro.org/lava/lava-dispatcher.git/tree/lava_ dispatcher/actions/boot/u_boot.py#n215
Did anyone already encountered this error in the past?
(I edited a jinja2 device type file and a jinja2 dictionary file as well to match my device's properties. The device type file is saved in /etc/lava-server/dispatcher-config/device-types/ and the device dictionary file is saved in /etc/lava-server/dispatcher-co nfig/devices/).
An error in those changes is the most likely cause.
https://validation.linaro.org/static/docs/v2/device-integration.html
Thank you for your help,
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
Hello,
I was running the version 2016.12 of LAVA. I did a simple install on my
Debian Stretch Desktop but Debian stable releases of LAVA do not receive updates to LAVA directly.
Today I installed lava-server from stretch-backports. I was expecting to get the 2018.2.1 version of LAVA as we can see here https://tracker.debian.org/pkg/lava-server, but the update I got was lava-server 2017.7.1 and lava-dispatcher 2017.7.1.
As explained in the link you mentioned: lava-server version in stretch-backport is 2017.1 If you want to get the latest version, you should the production repository as explained here: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#lava-...
Regards
Thank you for your answer Remi,
regards,
On 27 February 2018 at 15:39, Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
I was running the version 2016.12 of LAVA. I did a simple install on my
Debian Stretch Desktop but Debian stable releases of LAVA do not receive updates to LAVA directly.
Today I installed lava-server from stretch-backports. I was expecting to get the 2018.2.1 version of LAVA as we can see here https://tracker.debian.org/pkg/lava-server, but the update I got was lava-server 2017.7.1 and lava-dispatcher 2017.7.1.
As explained in the link you mentioned: lava-server version in stretch-backport is 2017.1 If you want to get the latest version, you should the production repository as explained here: https://validation. linaro.org/static/docs/v2/installing_on_debian.html#lava-repositories
Regards
-- Rémi Duraffort LAVA Team Linaro
-
Conrad Djedjebi -
Neil Williams -
Remi Duraffort