Hi Milosz,
Thanks for the support you have given. And I could able to achieve the scenario by changing the code from worker side as below
Navigate to the directory : cd /usr/lib/python3/dist-packages/lava_dispatcher
debian = { "TESTER_PS1": r"linaro-test [rc=$(echo $?)]# ", "TESTER_PS1_PATTERN": r"linaro-test [rc=(\d+)]# ", "TESTER_PS1_INCLUDES_RC": True, "boot_cmds": "boot_cmds", "line_separator": "\n", # for lava-test-shell "distro": "debian", "tar_flags": "--warning no-timestamp", "lava_test_sh_cmd": "/bin/bash", "lava_test_dir": "/lava-%s", "lava_test_results_part_attr": "root_part", "lava_test_results_dir": "/etc/lava-%s", "lava_test_shell_file": "~/.bashrc", }
I changed "lava_test_results_dir": "/etc/lava-%s", from "lava_test_results_dir": "/lava-%s", from the above code session. Somehow the lava_test_results_dir variable which we defined in the job definition is not getting override by the default value , that’s why we did the change. Can you post your code snippet from the worker ? and do you know why the job definition is not able to identify the lava_test_results_dir value ?
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 13 March 2023 14:50 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Sarath,
Sorry, I can't reproduce any of your issues. You need to debug yourself.
Best Regards, Milosz
On Mon, Mar 13, 2023 at 6:11 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Any update ?
Regards, Sarath P T
-----Original Message----- From: P T, Sarath Sent: 08 March 2023 15:53 To: 'Milosz Wasilewski' milosz.wasilewski@foundries.io Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: RE: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
Hi Milosz,
Now we could able to unpack the overlay in the path that we have given in the job definition. But after exporting the shell (export SHELL=/bin/bash) its not able to proceed with ". /<path_defined_in_definition>/lava-13030/environment" and "/<path_defined_in_definition>/lava-13030/bin/lava-test-runner /<path_defined_in_definition>/lava-13030/0 ". Below I am giving the job definition.
priority: high visibility: public device_type: industrial-mtda-simatic-ipc227e-01 visibility: public timeouts: job: minutes: 30 action: minutes: 20 connection: minutes: 20 job_name: SLLL_CI_MTDA_SIMATIC_IPC227E_DEPLOY_BOOT_TEST_JOB actions:
- deploy: to: overlay os: debian
- boot: method: minimal reset: true failure_retry: 2 auto_login: login_prompt: 'ebsy-isar login:' username: root password_prompt: "Password:" password: root prompts:
transfer_overlay: download_command: sleep 10; cd /home/test ; wget unpack_command: tar -C /home/test -xzf
- 'root@ebsy-isar:~#'
- test: role:
timeout: minutes: 5 definitions:
- node1
- repository: metadata: description: basic test for some devices on board format: Lava-Test Test Definition 1.0 name: kernel-version os: - debian run: steps: - cd /usr/libexec/ebsy-qa-suites/swupdate - ./swupdate_new.sh from: inline name: mtda-restart path: inline/mtda.yaml
context: lava_test_results_dir: /home/test/lava-%s test_character_delay: 10 tags:
- slll-industrial-mtda-simatic-ipc227e-01
timeouts: action: minutes: 20 connection: minutes: 20 job: hours: 7 visibility: public job_name: SLLL_X86_TEST_JOB metadata: Description: '"Lava jobs for deploy, boot and usb test"' DEVICES: slll-simatic-ipc227e-mtda-01
Regards, Sarath P T
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@foundries.io Sent: 01 March 2023 14:27 To: P T, Sarath Sarath_PT@mentor.com Cc: lava-users@lists.lavasoftware.org; Bhola, Bikram (PLM) bikram.bhola@siemens.com Subject: Re: [Lava-users] Re: Not able to unpack the overlay other than "/" directory
On Wed, Mar 1, 2023 at 5:51 AM P T, Sarath Sarath_PT@mentor.com wrote:
Hi Milosz,
Yes it’s a strange behaviour that there is no command sent over serial to start overlay decompression. And is there any server configuration changes you made for accomplishing it ?
No, I'm running vanilla LAVA dispatcher in a container from dockerhub https://hub.docker.com/r/lavasoftware/lava-dispatcher/
Best Regards, Milosz