lava-users

lava-users@lists.lavasoftware.org

1 participants
912 discussions

by cnspring2002

Dear all, I have one issue when use one qualcomn's development board: - test: definitions: - from: inline name: auto_test path: inline/auto_test.yaml repository: metadata: description: run format: Lava-Test name: run run: steps: - lava-test-case "Android_Serial_Case" --shell "./test.py" docker: image: myimage local: true timeout: minutes: 1600 The test.py is from our customer, when run it, it show the error: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 265, in open self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK) FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.7/site-packages/serial/serialutil.py", line 240, in __init__ self.open() File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 268, in open raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg)) serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' I have linked the board to pc, and can see the "/dev/ttyUSB0" in my pc, what happened here?

4 years

What's the suggestion for application which may need fuse in docker test shell?

by Larry Shen

Hi, We have a test which may need /dev/fuse when run in docker test shell, something like next: docker run -it --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfined hello What's the suggestion for this case? Thanks.

4 years, 1 month

Moving boot commands from definition to device for UUU boot action

by Westermann, Oliver

Hey, I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know. I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices? Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers! Best regards, Olli Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files] - boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]

4 years, 1 month

Re: [Lava-users] lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi, I had installed docker long back and therefore not remember how I installed it exactly but I think I used "apt-get install docker.io" Here is the docker version running on my system. anantha@anantha-buster:~$ docker version Client: Version: 18.09.1 API version: 1.39 Go version: go1.11.6 Git commit: 4c52b90 Built: Sun, 14 Jun 2020 22:12:29 +0200 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.09.1 API version: 1.39 (minimum version 1.12) Go version: go1.11.6 Git commit: 4c52b90 Built: Sun Jun 14 20:12:29 2020 OS/Arch: linux/amd64 Experimental: false Full log: https://paste.debian.net/1170559/ Will try with a fresh docker installation as in https://staging.validation.linaro.org/static/docs/v2/docker-admin.html#prer… From: K R, ANANTHA Sent: 06 November 2020 18:08 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org> Subject: RE: lava-docker-worker: docker OCI runtime error Hi all, I removed the "-init" flag passed to docker command in the /usr/lib/python3/dist-packages/docker_worker.py. After this the worker container started and is shown to be online in lava server web interface. Is this work around ok to be used ? I'm using the lava-docker-worker on a Debian buster (10.6) machine. Thank you, Anantha From: K R, ANANTHA Sent: 04 November 2020 20:37 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org<mailto:lava-users@lists.lavasoftware.org>> Subject: lava-docker-worker: docker OCI runtime error Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP<http://%3cMy-LAVA-server-IP>> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

4 years, 1 month

Re: [Lava-users] lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi all, I removed the "-init" flag passed to docker command in the /usr/lib/python3/dist-packages/docker_worker.py. After this the worker container started and is shown to be online in lava server web interface. Is this work around ok to be used ? I'm using the lava-docker-worker on a Debian buster (10.6) machine. Thank you, Anantha From: K R, ANANTHA Sent: 04 November 2020 20:37 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org> Subject: lava-docker-worker: docker OCI runtime error Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP<http://%3cMy-LAVA-server-IP>> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

4 years, 1 month

lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

4 years, 1 month

Re: [Lava-users] lava-docker-worker: how to customize?

by Philippe Mazet (OSS)

Thanks Milosz. Does that mean that a lava-docker-worker is designed to only run jobs which use "docker"? I would not like to modify all my legacy jobs which do not use the new "docker" thing. Also, I understood that this new "docker" in LAVA jobs was mainly aimed at Android testing. For Linux/yocto, that sounds like useless extra complexity (unless I miss something). -----Original Message----- From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Milosz Wasilewski Sent: Thursday, October 29, 2020 11:03 AM To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> Subject: [EXT] Re: [Lava-users] lava-docker-worker: how to customize? Caution: EXT Email On Thu, 29 Oct 2020 at 10:00, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> wrote: > > Hi All, > > I was exploring the new lava-docker-worker released with 2020.09. > It is pretty handy to start a slave, but I am wondering how to customize the slave image: > I need to add inside my own tools (like uuu), config files (like ser2net.conf), and also install additional packages. > How do you do this on your side? I think you're confusing 2 things here. The lava-docker-worker image is not supposed to run the jobs. For that you use 'docker: <image name>: in the job definition actions. This is the image that should contain flashing tools like uuu. As for ser2net I'm not sure what is the recommendation (Antonio, could you comment?). We're stil using host based ser2net. milosz > > Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue? > > Thanks, > > Philippe Mazet > > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist > s.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=04%7C01% > 7Cphilippe.mazet%40nxp.com%7Cde6159fe8c1e43cfcc0008d87bf1f211%7C686ea1 > d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637395626367151208%7CUnknown%7CTW > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6 > Mn0%3D%7C3000&sdata=gElRt2xv5DouqTeQUF6nPlP33MUKUs68ZT8LWmB67%2Fc% > 3D&reserved=0 _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav…

4 years, 1 month

lava-docker-worker: how to customize?

by Philippe Mazet (OSS)

Hi All, I was exploring the new lava-docker-worker released with 2020.09. It is pretty handy to start a slave, but I am wondering how to customize the slave image: I need to add inside my own tools (like uuu), config files (like ser2net.conf), and also install additional packages. How do you do this on your side? Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue? Thanks, Philippe Mazet

4 years, 1 month

Error while using uuu boot method

by DAS, BHARGAV

Hi Lava users, I am getting " Job error: Invalid job data: ['Unable to connect to shell - missing connections block.'] " error while submitting jobs which is using 'uuu' deploy and boot method. Same job I am using in a different server and there it is working perfectly. Both the servers are using same version. Please check the attached job yaml file (uuu-job.yaml) and the job log (uuu-job-fail-log.txt). Regards, Bhargav

4 years, 2 months

Job IMCOMPLETE for unknown reason

by Kever Yang

Hi For the same job, I may got 'complete'(for most case) and 'incomplete' in lava server dashboard, the logs are almost the same and both show that the job finished correctly and the result is pass. My question is: how is the server define the job as 'incomplete'? When I check the lava server log, I got the same error log for ALL 'complete' and 'incomplete' jobs(most of them are actually mark as complete in the dashboard result): 2020-10-10 09:40:58,386 DEBUG - rv1126-evb 2020-10-10 09:40:58,395 DEBUG -> rv1126-evb-01 (Idle, Unknown) 2020-10-10 09:40:58,395 DEBUG |--> [140442] scheduling 2020-10-10 09:40:58,486 INFO [140442] START => lava-slave247 (rv1126-evb-01) 2020-10-10 09:40:58,517 INFO [140442] lava-slave247 => START_OK 2020-10-10 09:41:09,539 DEBUG lava-logs => PING(20) 2020-10-10 09:41:13,537 INFO [140442] lava-slave247 => END (lava-run crashed, mark job as INCOMPLETE) 2020-10-10 09:41:13,759 ERROR [140442] Unable to dump 'description.yaml' 2020-10-10 09:41:13,759 ERROR [140442] Compressed data ended before the end-of-stream marker was reached Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 312, in _handle_end description = lzma.decompress(compressed_description) File "/usr/lib/python3.5/lzma.py", line 340, in decompress raise LZMAError("Compressed data ended before the " _lzma.LZMAError: Compressed data ended before the end-of-stream marker was reached 2020-10-10 09:41:13,763 DEBUG lava-slave241 => PING(20) Thanks, - Kever

4 years, 2 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users