lava-users

lava-users@lists.lavasoftware.org

3 participants
946 discussions

by Conrad Djedjebi

Good morning everyone, I would like to show you the following : Did anyone encounter that error in the past while trying to log into a local standalone master instance of lava ? I installed LAVA 2018 and the localhost page in being opened without issues. Things get worst when I try to login. I am getting that error on chromium and Firefox. Both of them have cookies enabled. Best regards,

8 years, 1 month

Error while submitting a LAVA Test Job Definition | Standalone LAVA Master installation

by Conrad Djedjebi

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,

8 years, 1 month

Does LAVA v2 support test image dummy deployed

by Arthur She

Hi, I have an impression that we can have test image "dummy" deployed once I am sure the image in the device is bootable. That will save time for downloading and flashing to the device. Does it still be supported in LAVA v2? Thanks, Arthur

8 years, 1 month

Re: [Lava-users] set up issue

by Christopher McClellan

Hermanth, You were able to install on stretch? I was attempting to do so, but the python3-django-auth-ldap package wasn't available on anything but sid. Did you run into the same issue? Regards, Chris > Date: Tue, 27 Feb 2018 14:10:46 +0530 > From: Hemanth K V <kv.hemanth.mys(a)gmail.com> > To: Lava Users Mailman list <lava-users(a)lists.linaro.org> > Subject: [Lava-users] set up issue > Message-ID: > <CAEua01SDZE6=7+rgnr6+1WA-j3Z3g2ECywP0qtT0xR8Z9GE9Gw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello Lava-Users, > > After following the setup of LAVA on Debian 9 stretch and when we try to > login from UI we face the following error Ref > https://validation.linaro.org/static/docs/v2/installing_on_debian.html > > $ sudo apt install postgresql > $ sudo apt install lava-server > > If the default Apache configuration from LAVA is suitable, you can enable > it immediately: > > $ sudo a2dissite 000-default > $ sudo a2enmod proxy > $ sudo a2enmod proxy_http > $ sudo a2ensite lava-server.conf > $ sudo service apache2 restart > > Forbidden (403) > > CSRF verification failed. Request aborted. > > You are seeing this message because this site requires a CSRF cookie when > submitting forms. This cookie is required for security reasons, to ensure > that your browser is not being hijacked by third parties. > > If you have configured your browser to disable cookies, please re-enable > them, at least for this site, or for 'same-origin' requests. > > > Is there anything missing from the setup. > > > Thanks, > > Hemanth.

8 years, 1 month

User notifications in LAVA

by Xu, Hongyu

Hi all, Why I can't receive the email when I use the 'User notifications' in LAVA ? notify: criteria: status: canceled verbosity: quiet recipients: - to: method: email email: hongyu.xu(a)hxt-semitech.com<mailto:hongyu.xu@hxt-semitech.com> or notify: criteria: status: complete verbosity: quiet recipients: - to: user: '1680141' method: email [cid:image001.png@01D3AFE4.37D7A500] Best Regards XuHongyu This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.

8 years, 1 month

Re: [Lava-users] set up issue

by Tim Jaacks

This is a django configuration issue. I don’t understand why this case (it is very common, obviously) is not handled in the LAVA documentation explicitly. There is a short hint, though, here: https://validation.linaro.org/static/docs/v2/pipeline-debug.html#using-loca… You have to add these two variables to /etc/lava-server/settings.conf: "CSRF_COOKIE_SECURE": false, "SESSION_COOKIE_SECURE": false I achieved this using the following commands: sudo apt-get install jq jq '.CSRF_COOKIE_SECURE=false | .SESSION_COOKIE_SECURE=false' /etc/lava-server/settings.conf > /tmp/settings.conf && mv /tmp/settings.conf /etc/lava-server/settings.conf sudo chown root:root /etc/lava-server/settings.conf sudo service lava-server-gunicorn restart Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com SOLUTIONS THAT COMPLETE! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz

8 years, 1 month

set up issue

by Hemanth K V

Hello Lava-Users, After following the setup of LAVA on Debian 9 stretch and when we try to login from UI we face the following error Ref https://validation.linaro.org/static/docs/v2/installing_on_debian.html $ sudo apt install postgresql $ sudo apt install lava-server If the default Apache configuration from LAVA is suitable, you can enable it immediately: $ sudo a2dissite 000-default $ sudo a2enmod proxy $ sudo a2enmod proxy_http $ sudo a2ensite lava-server.conf $ sudo service apache2 restart Forbidden (403) CSRF verification failed. Request aborted. You are seeing this message because this site requires a CSRF cookie when submitting forms. This cookie is required for security reasons, to ensure that your browser is not being hijacked by third parties. If you have configured your browser to disable cookies, please re-enable them, at least for this site, or for 'same-origin' requests. Is there anything missing from the setup. Thanks, Hemanth.

8 years, 1 month

x86 sample job

by Hemanth K V

Hello Lava Users, Trying to setup the x86 based board to our local lava farm to execute tests. Want to boot the target with pxe based mechanism .Trying to follow the job definition https://staging.validation.linaro.org/scheduler/job/210084/definition .With this facing the following error when running the job.Let me know if i am missing anything with job defination or device defination . File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 563, in validate self.internal_pipeline.validate_actions() File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 201, in validate_actions action.validate() File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/actions/boot/ipxe.py", line 221, in validate elif self.parameters['commands'] not in device_methods[self.parameters['method']]: TypeError: unhashable type: 'list' Device dictionary defination is Device dictionary yaml: connection_command: telnet localhost 8021 extends: x86.jinja2 Thanks, Hemanth.

8 years, 2 months

LAVA V2 hangs over non-existent job!

by Zoran S

Hello to LAVA admins, You have fatal error in Lava V2. I submitted job, which hangs in submitted state indefinitely. I also see the non-existent job 92 (which is deleted) running there?! http://localhost:8080/scheduler/device/bbb01 254 2018-02-21 12:05 Reserved → Running — Job 92 running 253 2018-02-21 12:04 Idle → Reserved — Reserved for job 92 252 2018-02-21 12:03 Running → Idle — Job 91 cancelled 251 2018-02-21 12:03 Reserved → Running — Job 91 running 250 2018-02-21 12:03 Idle → Reserved — Reserved for job 91 249 2018-02-21 11:33 Running → Idle — Job 89 has ended. Setting job status Incomplete But when I look to this local pointer: http://localhost:8080/admin/lava_scheduler_app/testjob/ 102 Submittednobodylessbeaglebone-black -Feb. 21, 2018, 1:07 p.m.-- 76 Incompletenobodylessbeaglebone-black bbb01 (Running, health Unknown)Feb. 20, 2018, 9:50 a.m.Feb. 20, 2018, 9:50 a.m.Feb. 20, 2018, 9:55 a.m. 49 Completenobodylessqemu qemu01 (Idle, health Unknown)Feb. 16, 2018, 10:44 a.m.Feb. 16, 2018, 10:44 a.m.Feb. 16, 2018, 10:50 a.m. 43 Completenobodylessqemu qemu01 (Idle, health Unknown)Feb. 16, 2018, 8:42 a.m.Feb. 16, 2018, 8:43 a.m.Feb. 16, 2018, 8:49 a.m. How to force submitted job to be active job (from both CLI and GUI)? How to delete nonexistent jobs (from both CLI and GUI)? Thank you, Zoran

8 years, 2 months

Lava dispatcher long test runs executions in V.L.O.

by Anibal Limon

Hi, I created a Piglit test definition [1] before i try to test it out into the V.L.O. i used test-runner to make a run locally (db410c) without lava-dispatcher, the run took ~2 hours 5 minutes [2] (wo download/flash) after that i tried to execute into the V.L.O. and it consumes 8 hours of execution and then finalize with a timeout, the test didn't reach the end and was able to execute only 14486 tests of 39249. So i download the definition and executed the lava-run command in my desktop and the full test execution was in ~2 hours 38 minutes that makes sense because needs to download and flash the boot and rootfs images. [4] I introduced a time call for measure the piglit time execution in test-runner and lava-dispatcher and the exec times are the same ~96 minutes in both executions, search for ' Thank you for running Piglit' in the logs [2][5]. I noticed when i ran lava-run into my desktop the CPU usage increases to 100% when reaches the step of actually running the test [6], i made some debugging and discover that the manner to get the results and notifications from serial console is using pexpect and certain regexes, i attached the gdb to the python process and found that the regexes executes over the whole serial buffer in very short intervals [7] That could be the reason of the delay in the test execution since the Piglit command takes the same time to run with test-runner and lava-dispatcher. Best regards, Anibal [1] https://git.linaro.org/qa/test-definitions.git/tree/automated/linux/piglit/… [2] http://qcom-hackbox.linaro.org:8090/stdout_testrunner.log.gz [3] https://lkft.validation.linaro.org/scheduler/job/101274 [4] http://qcom-hackbox.linaro.org:8090/stdout_dispatcher.log.gz [5] http://qcom-hackbox.linaro.org:8090/stdout_dispatcher_time.log.gz [6] http://qcom-hackbox.linaro.org:8090/lava_run_top.log [7] http://qcom-hackbox.linaro.org:8090/lava_run_gdb.log [8] https://git.linaro.org/lava/lava-dispatcher.git/tree/lava_dispatcher/action…

8 years, 2 months

← Newer
1
...
71
72
73
74
75
76
77
...
95
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users