Hi Team,
Facing an issue related to the LAVA job timeout. Job is not exiting even after the timeout , its continuously loading after the job completion. Below I am giving my observations:
1. A LAVA job has executed with the job id : 3959
2. And under the worker I am getting the log as shown below :
2022-02-22 23:19:09,534 DEBUG [3959] dispatch: None
2022-02-22 23:19:09,535 DEBUG [3959] env : {'purge': True, 'overrides': {'LC_ALL': 'C.UTF-8', 'LANG': 'C', 'PATH': '/usr/local/bin:/usr/local/sbin:/bin:/usr/bin:/usr/sbin:/sbin'}}
2022-02-22 23:19:09,535 DEBUG [3959] env-dut : None
2022-02-22 23:19:09,584 INFO [3959] RUNNING => server
2022-02-22 23:19:09,850 INFO [3834] FINISHED => server
2022-02-22 23:19:10,087 ERROR [3834] -> server error: code 503
2022-02-22 23:19:10,088 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-22 23:19:28,651 INFO PING => server
2022-02-22 23:19:29,142 INFO [3834] FINISHED => server
2022-02-22 23:19:29,775 ERROR [3834] -> server error: code 503
2022-02-22 23:19:29,776 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-22 23:19:48,652 INFO PING => server
2022-02-22 23:19:49,146 INFO [3834] FINISHED => server
2022-02-22 23:19:49,391 ERROR [3834] -> server error: code 503
2022-02-22 23:19:49,391 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-22 23:20:08,653 INFO PING => server
2022-02-22 23:20:09,171 INFO [3959] running -> finished
2022-02-22 23:20:09,224 INFO [3834] FINISHED => server
2022-02-22 23:20:09,525 ERROR [3834] -> server error: code 503
2022-02-22 23:20:09,525 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-22 23:20:28,654 INFO PING => server
2022-02-22 23:20:29,147 INFO [3834] FINISHED => server
2022-02-22 23:20:29,756 ERROR [3834] -> server error: code 503
2022-02-22 23:20:29,756 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
Seems after the job execution somewhere the communication between server and worker is getting interrupted. It will be a great help if you people are looking into the issue and hope you will find the solution for the same.
Regards
Sarath P T
Hi,
My LAVA job status still shows "Running" even when the job is completed and
status does not change even after 24 hours.
Due to that my other Job's pending from that dispatcher targets.
My dispatcher shows these errors for
/var/log/lava-dispatcher/lava-worker.log i.e "
https://pastebin.com/46WFtAin"
Please can someone let me know a solution to fix this issue?
Regards,
Koti
Hi Cano Pablo,
If my understanding is correct, you may want to flash the images in boot
action.
We can flash the same using the below boot action.
"
actions:
- deploy:
timeout:
minutes: 10
to: flasher
images:
image:
url: file: <firmware path>
- boot:
method: bootloader
bootloader: u-boot
commands:
- ' xxxxx'
prompts:
- 'xxxxx'
timeout:
minutes: 10
"
1. Please provide your flash script under
/etc/lava-server/dispatcher-config/devices/<device.jinja2> file as
mentioned below under "flasher_deploy_commands"
Example: (Note: {IMAGE} is the file mentioned in Deply action
i.e "url: file: <firmware path>"
{% set flasher_deploy_commands = ['/1.py',
'sleep 10',
'/2.py',
'sleep 10',
'/flash.sh "{IMAGE}" &',
'sleep 2',
'sleep 2'] %}
2. Please mention your bootmethod and bootloader as per your requirement.
Regards,
Koti
On Wed, 2 Feb 2022 at 05:30, <lava-users-request(a)lists.lavasoftware.org>
wrote:
> Send Lava-users mailing list submissions to
> lava-users(a)lists.lavasoftware.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> lava-users-request(a)lists.lavasoftware.org
>
> You can reach the person managing the list at
> lava-users-owner(a)lists.lavasoftware.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lava-users digest..."
>
> Today's Topics:
>
> 1. Flashrom (Cano, Pablo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 1 Feb 2022 23:21:42 +0000
> From: "Cano, Pablo" <Pablo.Cano(a)Resideo.com>
> Subject: [Lava-users] Flashrom
> To: "lava-users(a)lists.lavasoftware.org"
> <lava-users(a)lists.lavasoftware.org>
> Message-ID: <SN4PR22MB33174DEF13E85267D949A52B8B269(a)SN4PR22MB3317.nam
> prd22.prod.outlook.com>
> Content-Type: multipart/alternative; boundary="_000_SN4PR22MB33174D
> EF13E85267D949A52B8B269SN4PR22MB3317namp_"
>
> Hi,
> Someone knows how to implement flashrom in the booting action of the
> device type?
>
Hi,
I'm starting to work with LAVA and I want to know if there is a template for a Texas Instrument microcontroller like CC1312. Also, I want to know if someone try to connect a DUT with CHEETAH that is a SPI host adapter. If so, what is the method to communicate it with LAVA?
Best,
Pablo
The IMXRT1050 seems to be already supported, including jlink support.
https://git.lavasoftware.or/lava/lava/-/blob/master/etc/dispatcher-config/d…
And since the device-type template already exists in LAVA, it should not be too complicated to get started with it.
However, I am not using this type of device myself, so I can't help more.
Philippe
From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Cano, Pablo
Sent: Friday, January 21, 2022 10:36 PM
To: lava-users(a)lists.lavasoftware.org
Subject: [Lava-users] Add new device NXP rt1050
Hi,
I'm starting to work with LAVA and I read the documentation about add a new device is more difficult rather than use some templates. So, my question is if there is a template to use with a microprocessor like rt1050 that has an architecture ARM7vE-M. Also, I need to communicate to this unit with J-link and UART, is possible to use direct communication or I need to connect via the network.
Hi,
I'm starting to work with LAVA and I read the documentation about add a new device is more difficult rather than use some templates. So, my question is if there is a template to use with a microprocessor like rt1050 that has an architecture ARM7vE-M. Also, I need to communicate to this unit with J-link and UART, is possible to use direct communication or I need to connect via the network.
Hi,
Recently my "lava-worker" host name was changed and showed the same offline
in Lava-server.
Is there any easy way to edit the old hostname with the new hostname (in
lava-server side software) to bring back the lava-worker/dispatcher online ?
Regards,
Koti
Hi,
I plan to install the 2021.10 lava-dispatcher instead of the 2021.11 latest
version.
I am unable to install the 2021.10 lava-dispatcher version but able to
install 2021.11 using "apt install lava-dispatcher"
Is there any way to install the 2021.10 lava-dispatcher at this time? Or
do we always need to install the latest versions?
Regards,
koti
Hi Nagerndra,
I would recommend send a patch if the issue is resolved so that the LAVA
team will review/check it.
Regards,
Koti
On Thu, 25 Nov 2021 at 17:30, <lava-users-request(a)lists.lavasoftware.org>
wrote:
> Send Lava-users mailing list submissions to
> lava-users(a)lists.lavasoftware.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.lavasoftware.org/mailman/listinfo/lava-users
> or, via email, send a message with subject or body 'help' to
> lava-users-request(a)lists.lavasoftware.org
>
> You can reach the person managing the list at
> lava-users-owner(a)lists.lavasoftware.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lava-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Constant failure_retry does not exist in the device
> config 'constants' (Nagendra Singamsetti)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 24 Nov 2021 18:02:59 +0530
> From: Nagendra Singamsetti <nag.singam91(a)gmail.com>
> To: lava-users(a)lists.lavasoftware.org
> Subject: Re: [Lava-users] Constant failure_retry does not exist in the
> device config 'constants'
> Message-ID:
> <CAFhg_Wtt3+AnYRLLO7nm2u8uiYKLFPHaS7_Q5LKvah=
> 0Z_vsSg(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi All ,
> The Issue got solved by updating the latest change in base.jinja2
> device-type file.
>
> # Set the failure retry to default or override it failure_retry: {{
> failure_retry|default(1) }} # Override boot_retry boot_retry: {{
> boot_retry }}{% endblock constants -%}
>
> I am not sure why base.jinja2 is not updated during the 2021.10
> lava-server upgrade process. If any one got the same issue please try
> this change.
>
> thanks
>
> Regards
>
> Nagendra S
>
>
> On Wed, Nov 24, 2021 at 1:19 PM Nagendra Singamsetti <
> nag.singam91(a)gmail.com>
> wrote:
>
> > Hi All,
> >
> > I got struck with strange issue with latest version 2021.10
> >
> >
> > - *error_msg*: Constant failure_retry does not exist in the device
> > config 'constants' section.
> > - *error_type*: Configuration
> >
> > ConfigurationError: The LAVA instance is not configured correctly. Please
> > report this error to LAVA admins.
> >
> > My setup is working fine with 2021.05. But after upgrading with the
> latest
> > version 2021.10 none of the jobs are not working. Always it raises the
> > Exception called Configuration Error.
> >
> > Looking forward to your kind response!!!
> >
> >
> > Regards
> > Nagendra S
> >
> >
> >
>
