lava-users

lava-users@lists.lavasoftware.org

1 participants
912 discussions

LAVA: How to link Requirements/"Any web page" page URL's to LAVA test cases

by koti koti

Hi, How can I link the Requirement page (any web page) URL to LAVA test cases ? 1. I just want to see that web page URL in test case results page log after execution of test. Do I need to add that web page URL as metadata data in while writing the test definitions? Regards, Koti

4 years, 2 months

Re: [Lava-users] LAVA: How to link Requirements/"Any web page" page URL's to LAVA test cases

by koti koti

Hi, I guess we may need to include under "metadata:" in yaml file, right? is my understanding correct? so that we can see the same in "Details" section under the corresponding Job. (Ex: https://staging.validation.linaro.org/scheduler/job/280173 . Attached the screen shot) Example: ####### metadata: Testcase ID : TestCase_ID: xxxxx Requirement Path: Requirement_URL_Page : XXXXX Regards, Koti On Mon, 19 Oct 2020 at 15:05, koti koti via groups.io <kotisoftwaretest= gmail.com(a)groups.io> wrote: > Hi, > > How can I link the Requirement page (any web page) URL to LAVA test cases ? > > 1. I just want to see that web page URL in test case results page log after > execution of test. > > Do I need to add that web page URL as metadata data in while writing the > test definitions? > > Regards, > Koti > > > -=-=-=-=-=-=-=-=-=-=-=- > Groups.io Links: You receive all messages sent to this group. > View/Reply Online (#964): https://groups.io/g/kernelci/message/964 > Mute This Topic: https://groups.io/mt/77654665/4395798 > Group Owner: kernelci+owner(a)groups.io > Unsubscribe: https://groups.io/g/kernelci/unsub [ > kotisoftwaretest(a)gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- > > >

4 years, 2 months

LAVA : relays and PDU's info for dragonboard-845 DUT in India

by koti koti

Hi, I have connected my Dragonboard-845 DUT to Lava Dispatcher (Dispatcher is "raspberry pi 4" SBC) Now I need to set up "Remote Power Control" and "Set target into Program mode" . Please can someone let me know the required hardware list like "Remote PDU (Remote Power Distribution)" and "Relays" units purchase URL's in India for below requirement. 1. Power ON/Power OFF/reboot the target from Lava Dispatcher. ( Hope this functionality may be fully filled by the PDU. Can some let me know low cost PDU's URLs with 2 outlets) 2. set target into Programing mode ( to flash the images) (Is this functionality can be done by any relays? if yes, Please can someone let me know the available relays URL's in India) Note: 1. I have found a couple of Relays URL's ( https://www.robot-electronics.co.uk/products/relay-modules/ethernet-relay/e…) . * But these are not available in India.* Regards, Koti

4 years, 2 months

Issues about XMLRPC & lavacli.

by Larry Shen

Hi, guys, We find an issue related to job submit: 1) One team use "lavacli" to submit request, and sometimes it will report next: 07-Sep-2020 16:37:35 Unable to connect: HTTPConnectionPool(host='lava-master.sw.nxp.com', port=80): Read timed out. (read timeout=20.0) Looks this error happens at next, what do you think about this issue? try: # Create the Transport object parsed_uri = urlparse(uri) transport = RequestsTransport( parsed_uri.scheme, config.get("proxy"), config.get("timeout", 20.0), config.get("verify_ssl_cert", True), ) # allow_none is True because the server does support it proxy = xmlrpc.client.ServerProxy(uri, allow_none=True, transport=transport) version = proxy.system.version() except (OSError, xmlrpc.client.Error) as exc: print("Unable to connect: %s" % exc2str(exc)) return 1 2) Another team write their own python code using XMLRPC to submit job, did something like next, it reports next: ERROR in XMLRPC.py:submitJob:63 msg: Failed to submit job, reason: <ProtocolError for chuan.su:chuan.su@lava-master.sw.nxp.com/RPC2: 502 Bad Gateway>! try: job_id = self.connection.scheduler.submit_job(job) self.logger.debug("Successed to submit job , job_id: %d, platform; %s!",job_id,platform) return job_id except Exception as e: self.logger.error("Failed to submit job, reason: %s!",str(e)) return None We are currently using lava server version 2020.08, guys told me in the past days, we also encountered similar, but with very low probability. But recently it becomes very high probability. I'd like to know if possible this will related to your changes to gunicorn eventlet? Or other possible reasons? Thanks, Larry

4 years, 2 months

Usb bus circulated issue for android.

by Larry Shen

Hi, guys, We found a blocking issue for android test, the story is next: 1. job #1 with device #1 is running for about 12 hours, during its run, it will restart the boards many times, then the usb path will e.g. start from /dev/bus/usb/003/001 to /dev/bus/usb/002, then /dev/bus/usb/003...... finally /dev/bus/usb/127. You know, the max number here will be 127, so, if device reset again, the number will back to 001. Adb devices in container 1: $ adb devices List of devices attached 040c41d4d72d7393 device 2. job #2 with device #2 starts run during the job #1 still running, then E.g. it will mknod /dev/bus/usb/003/016 to another docker-test-shell container, also cgroup privilege added. But as the /dev/bus/usb/003/016 was once used by job #1, and this node won't be deleted from docker-test-shell container. So, we find high probability the device #2 was seen in job #1's docker-test-shell container (Checked with adb devices). Now, adb devices in container 2: $adb devices List of devices attached After above, adb devices in container 1: $ adb devices List of devices attached 040c41d4d72d7393 device 23305a0a5c85d936 device This becomes a big issue for our parallel android test. In fact, in the old LXC days, we also find similar issues, so we made a workaround in our local: https://github.com/atline/lava-docker-slave/blob/66f15d9da88912fc929fef5213… In this patch, we also monitor "remove", ENV{ID_SERIAL_SHORT}, that is "if a usb leaved, let it delete the node". But, I don't know for which reasons, in current version(2020.08), now I can just monitor "remove" in udev, can't match "remove + ENV{ID_SERIAL_SHORT}" correctly. So, to make our local android run could work in a short time, we did a patch as next: # diff __init__.py.bak __init__.py 157,158c157,158 < "mkdir -p %s && mknod %s c %d %d || true" < % (os.path.dirname(node), node, major, minor), --- > "mkdir -p %s && rm -f %s/* && mknod %s c %d %d || true" > % (os.path.dirname(node), os.path.dirname(node), node, major, minor), Now, no issue happens in our side, but it looks this is somewhat not universal? So, I'm here to ask the question, have you ever found this issue? And what's your thought on this?

4 years, 3 months

U-boot reset Interactive test nethod

by DAS, BHARGAV

Hi Lava users, I am facing some issues while using the interactive test method, for testing u-boot reset function. In v2019.11 this worked perfectly but currently while using v2020.07 and this features seems to be broken. Or am I missing something here. Here detailed description of the issue: We are testing the u-boot reset command below is the snippet of the job definition ... ... ... - name: mmcinfo command: mmcinfo successes: - message: "Erase Group Size:" failures: - message: "Unknown command " error: "Unknown command " - name: reset command: reset successes: - message: "Hit any key to stop autoboot" failures: - message: "Unknown command " error: "Unknown command " So in v2019.11 once the "Hit any key to stop autoboot" string was matched the target switched off (check screenshot "reset-snippet-v2019-11.PNG"). But this is not working in v2020.07, after the success message is matched the target is not switched off (check screenshot "reset-snippet-v2020-07.PNG"). Regards, Bhargav

4 years, 3 months

About customize query in job page.

by Larry Shen

Hi, all, I want to do a job search with owner, E.g. in https://validation.linaro.org/scheduler/alljobs 's search box, I input next: owner_query=qa-reports-bot But, it return nothing to me, all jobs filtered out. I wonder what's the correct input in this search box for "Custom query text"? Regards, Larry

4 years, 3 months

Adding new device issue

by Koturappa, Hemanth

Hello Lava-Users, When we try to add new device we are facing the error 500 Internal Server Error maximum recursion depth exceeded in comparison Oops, something has gone wrong! Recently we had updated the LAVA instance server to Debian10. The LAVA server version presently running on the instance is lava_admin@svr-ies-ce-lava:~$ dpkg -l | grep lava ii lava 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture metapackage ii lava-common 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture common ii lava-coordinator 2020.07.0002.g44e83009c+10+buster all LAVA coordinator daemon ii lava-dev 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture developer support ii lava-dispatcher 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture dispatcher ii lava-dispatcher-host 2020.07.0002.g44e83009c+10+buster all LAVA dispatcher host tools ii lava-server 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture server ii lava-server-doc 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture documentation ii lavacli 0.9.5-1 all LAVA XML-RPC command line interface As specified in https://stackoverflow.com/questions/3323001/what-is-the-maximum-recursion-d… should we try to increase python recursion limit to overcome this? Thanks, Hemanth.

4 years, 3 months

lavapdu-client throwing error

by P T, Sarath

Hi，Team, I want to control device power on/off/reboot by lavapdu ,but when I run “/usr/bin/pduclient --daemon 134.86.60.229 --hostname 134.86.254.45 --command reboot --port 10” Error sending command, wrong daemon hostname? Can you help me solve this problem? Pdudaemon run on the lava-server. Below giving the configuration file for pduclient. { "daemon": { "hostname": "0.0.0.0", "port": 16421, "dbhost": "127.0.0.1", "dbuser": "pdudaemon", "dbpass": "pdudaemon", "dbname": "lavapdu", "retries": 5, "logging_level": "INFO" }, "pdus": { "192.168.10.2": { "driver": "apc9210" }, "192.168.10.3": { "driver": "apc7952", "telnetport": 5023 }, "192.168.10.4": { "driver": "apc7952" }, "192.168.10.5": { "driver": "apc8959", "this": "that", "something": "else" }, "192.168.25.52": { "driver": "apc7952" } } } Regards Sarath P T

4 years, 3 months

Error encounterd while using u-boot-ums deploy method

by DAS, BHARGAV

Hi Lava users, I am trying to use the u-boot-ums deploy method. I have taken reference from this job : https://staging.validation.linaro.org/scheduler/job/277518/definition While submitting the job I am getting the following error: Job error: None of the deployment strategies accepted your deployment parameters, reasons given: overlay: "to" parameter is not "overlay" docker: 'docker' not in the device configuration deploy methods download: "to" parameter is not "download" downloads: "to" parameter is not "downloads" qemu-nfs: "nfs" is not in the device configuration deploy methods images: "to" parameter is not "tmpfs" iso: "to" was not in parameters, or "to" was not "iso-installer" fastboot: "to" parameter is not "fastboot" flasher: 'flasher' not in the device configuration deploy methods fvp: 'to' was not fvp lxc: "to" parameter is not "lxc" nbd: "to" parameter is not "nbd" nfs: "to" parameter is not "nfs" removable: "media" was not "sata", "sd", or "usb" vemsd: "to" parameter is not "vemsd" mps: "mps" was not in the device configuration deploy methods musca: "musca" was not in the device configuration deploy methods ssh: "to" parameter is not "ssh" tftp: "to" parameter is not "tftp" uboot-ums: "u-boot-ums" was not in the device configuration deploy methods" recovery-mode: 'recovery' not in the device configuration deploy methods uuu: "to" parameter is not "uuu" Please check the attached yaml file (u-boot-ums-def.yaml). ? Regards, Bhargav

4 years, 3 months

← Newer
1
...
20
21
22
23
24
25
26
...
92
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users