Hello,
if the prompt is "# " without more characters then in the lava job
definition you have to put "# ".
In fact, this won't work well because this string can be seen on other
places (like kernel logs).
The only solution here would be to change the prompt of the root filesystem
to make it a bit more unique.
Rgds
Le mer. 31 juil. 2019 à 13:53, Hemanth K V <kv.hemanth.mys(a)gmail.com> a
écrit :
> Hello Remi,
>
> First of all Thanks for support.Trying for matching the string "# "
> If we don't specify any escape or brackets then it is matching one of the
> kernel message logs and sending the username .Following is reference of
> auto_login defined in yaml.
> ***** hwi path: hwi version/minor get_device_info->hwi_get_value: read
> STRING value:
> device name Matched prompt #4: #
>
> auto_login:
> login_prompt: "buildroot login:"
> username: root
> password_prompt: "Password:"
> password: root
> prompts:
> - '# '
>
> On including escape it is waiting for
> auto-login-action: Wait for prompt ['\\(# \\)', 'Login incorrect', 'Login
> timed out'] (timeout 00:07:53). Following is reference of auto_login
> defined in yaml.
>
> auto_login:
> login_prompt: "buildroot login:"
> username: root
> password_prompt: "Password:"
> password: root
> prompts:
> - '\(# \)'
>
> Thanks,
> Hemanth.
>
> On Wed, Jul 31, 2019 at 3:25 PM Remi Duraffort <remi.duraffort(a)linaro.org>
> wrote:
>
>> Hello,
>>
>> which strin are you trying to match? " #", "#", "# "?
>> Just put that (without any escaping or brackets) in the list of prompts.
>>
>> Rgds
>>
>> Le mar. 30 juil. 2019 à 14:20, Hemanth K V <kv.hemanth.mys(a)gmail.com> a
>> écrit :
>>
>>>
>>> Hello Lava Users,
>>>
>>> The target on which I am trying to run tests from LAVA has # prompt
>>> after login.
>>> As specified in Documentation
>>> https://lava.collabora.co.uk/static/docs/v2/actions-boot.html?highlight=pro…
>>>
>>> - boot:
>>> prompts:
>>> # escape the brackets to ensure that the prompt does not match
>>> # kernel debug lines which may mention initramfs
>>> - '\(initramfs\)'
>>>
>>> in the job definition I am including -
>>> boot:
>>> .....
>>> failure_retry: 4
>>> prompts:
>>> - '\(# \)'
>>>
>>> But in the job execution log getting "*auto-login-action: Wait for prompt ['\\(# \\)', 'Login incorrect', 'Login timed out'] (timeout 00:07:52)*".
>>>
>>> Also if we want to debug while running the job which will be the best possible approach to follow.
>>> In the Documentation got information on "Debugging Django issues" which states two settings are required in/etc/lava-server/settings.conf
>>>
>>>
>>> - "DEBUG": true,
>>> - "USE_DEBUG_TOOLBAR": true,
>>>
>>> Thanks,
>>> Hemanth.
>>>
>>> _______________________________________________
>>> Lava-users mailing list
>>> Lava-users(a)lists.lavasoftware.org
>>> https://lists.lavasoftware.org/mailman/listinfo/lava-users
>>
>>
>>
>> --
>> Rémi Duraffort
>> LAVA Team, Linaro
>>
>
--
Rémi Duraffort
LAVA Team, Linaro
Hello Lava Users,
The target on which I am trying to run tests from LAVA has # prompt after
login.
As specified in Documentation
https://lava.collabora.co.uk/static/docs/v2/actions-boot.html?highlight=pro…
- boot:
prompts:
# escape the brackets to ensure that the prompt does not match
# kernel debug lines which may mention initramfs
- '\(initramfs\)'
in the job definition I am including -
boot:
.....
failure_retry: 4
prompts:
- '\(# \)'
But in the job execution log getting "*auto-login-action: Wait for
prompt ['\\(# \\)', 'Login incorrect', 'Login timed out'] (timeout
00:07:52)*".
Also if we want to debug while running the job which will be the best
possible approach to follow.
In the Documentation got information on "Debugging Django issues"
which states two settings are required
in/etc/lava-server/settings.conf
- "DEBUG": true,
- "USE_DEBUG_TOOLBAR": true,
Thanks,
Hemanth.
Hello Denis,
in the timeouts dictionary, you can specify a connections dictionary.
So something like this should work:
timeouts:
connections:
overlay-unpack:
minutes: 10
See
https://docs.lavasoftware.org/lava/actions-timeout.html#connection-timeout
Le mer. 24 juil. 2019 à 14:30, Denis HUMEAU <denis.humeau(a)st.com> a écrit :
> Hi Rémi,
>
>
>
> Where do you set a connection timeout? In the job, in the device
> description?
>
> I didn’t find anything explicit in LAVA help.
>
>
>
> Denis
>
>
>
> *From:* Remi Duraffort <remi.duraffort(a)linaro.org>
> *Sent:* mercredi 24 juillet 2019 14:23
> *To:* Denis HUMEAU <denis.humeau(a)st.com>
> *Cc:* Lava-users(a)lists.lavasoftware.org
> *Subject:* Re: [Lava-users] overlay-unpack timeout error
>
>
>
> Hello Denis,
>
>
>
> have you tried settings the connection timeout? IIRC lava is expecting the
> board to send something and will timeout if not receiving anything during
> "connection timeout" seconds.
>
>
>
>
>
> Rgds
>
>
>
> Le mar. 23 juil. 2019 à 08:58, Denis HUMEAU <denis.humeau(a)st.com> a
> écrit :
>
> Hello Rémi,
>
>
>
> Here is a plain log corresponding to the case described by Philippe.
>
> Let me know if you need more.
>
>
>
> Denis
>
>
>
> *From:* Lava-users <lava-users-bounces(a)lists.lavasoftware.org> *On Behalf
> Of *Remi Duraffort
> *Sent:* lundi 22 juillet 2019 17:42
> *To:* Philippe BEGNIC <philippe.begnic(a)st.com>
> *Cc:* Lava-users(a)lists.lavasoftware.org
> *Subject:* Re: [Lava-users] overlay-unpack timeout error
>
>
>
> Hello Philippe,
>
>
>
> could you send the raw logs?
>
>
>
>
>
> Rgds
>
>
>
> Le ven. 19 juil. 2019 à 09:34, Philippe BEGNIC <philippe.begnic(a)st.com> a
> écrit :
>
> Hello everyone,
>
>
>
>
>
> I have got an error in a lava job during to overlay unpacking operations.
>
>
>
> This happen with jobs that flash the DUT before executing the tests. When the partitions are flashed on the DUT, I reboot the boards.
>
>
>
> After kernel has started, the kernel boot prompt is detected. Then the commands to downloads the tests overlay are launched. ( wget ... )
>
> But in my case, these commands are not immediately executed, because the DUT is beeing resizing the root filesystem to fit available disk space
>
> on the SDCard.
>
>
>
> This operation take time ( depending on capacity and characteristics of the SDCard), and cause overlay-unpack <https://citools.st.com/results/testcase/2039053> to fail with a timeout error,
>
> because the command wget is not executed in the expected time ( 30 sec is the default time ).
>
>
>
> I have tried to add a time out settings in the transfer_overlay part of my jobs, but this has no effect.
>
>
>
>
>
> Is it possible to set specific "timeout trigger" for the "overlay-unpack" operation ?
>
>
>
> My Lava version: *2019.01+stretch*
>
>
>
> Best regards
>
>
>
> Philippe Begnic
>
> STMicroelectronics
>
>
>
> _______________________________________________
> Lava-users mailing list
> Lava-users(a)lists.lavasoftware.org
> https://lists.lavasoftware.org/mailman/listinfo/lava-users
>
>
>
>
> --
>
> Rémi Duraffort
>
> LAVA Team, Linaro
>
>
>
>
> --
>
> Rémi Duraffort
>
> LAVA Team, Linaro
>
--
Rémi Duraffort
LAVA Team, Linaro
Hi,
I'm trying to write a test definition that contains a repeat block (boot / test) as described in the help section.
However the repeat block gives me the syntax error:
"Invalid definition: extra keys not allowed @ data['actions'][2]['repeat']"
I then tried using https://git.lavasoftware.org/lava/lava/blob/master/lava_dispatcher/tests/sa… as an example and I get the same error message with the repeat.
Is this something that is expected to work? I would like to use repeat blocks for some soak tests that I am writing.
Pete
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hello,
I am working with Denis HUMEAU for STMicroelectronics.
I have a problem to perform several reboot with LAVA job when I am using an image with requested login.
I do not understand why 'root' login is sent to device under test when the prompt is received (lines 941, 942, 943, 944 in job_43624.log file). 'root' login should be sent only when a 'login_prompt' is received (like in lines 696, 697, 698, 699, 701, 702 in job_43624.log file).
Could you help me to solve this problem, please ?
Regards,
[Description: Description: Description: Description: Description: Description: logo_big5]
Jerome BESNARD | TINA: 166 7142 | Tel: +33 (0)244027142 | Mobile: +33 (0)623392912
MDG | SW Validation Ingineer
Hello everyone,
I have the following LAVA setup:
LAVA server - 1 LAVA worker - 16 DUTs
The LAVA server and the LAVA worker are located in my company network (172.20.0.0/16).
The DUTs are connected to the LAVA worker in a local network (192.168.20.0/24).
Thus, the DUTs are not accessible from outside the worker.
What is a good way to allow for hacking sessions to a DUT (let's say 192.168.20.247) from the company network?
I can think of the following solutions:
1. Use SSH forwarding on lava-worker:
ssh -g -L 50000:localhost:22 -N root(a)192.168.20.247
2. Forward the SSH port via netcat on lava-worker:
nc -l -p 50000 -c "nc 192.168.20.247 22"
3. Forward the SSH port via iptables on lava-worker:
iptables -t nat -A PREROUTING -p tcp --dport 50000 -j DNAT --to 192.168.20.247:22
All of these make the device accessible via "ssh -p 50000 root@lava-worker" from the company network. So far, so good.
However, in an ideal world this forwarding would be active only during the hacking session, so that in normal test jobs the DUT is not accessible.
Is there a way to achieve this? Does anyone have experience with such a scenario? How do you handle DUT access for hacking sessions?
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
WE MAKE IT YOURS!
Sitz der Gesellschaft: D-21079 Hamburg
Registergericht: Amtsgericht Hamburg, HRB 60514
Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
Hello LAVA experts,
I need your help for a more complex test we would need to run.
We'd like to test a gateway node that talks to remote sensors.
* the gateway node is a Cortex-A like (E.g.: RPi3) board
* sensors might be a mixture of Cortex-M (non-Linux) and Cortex-A (Linux) devices
* communication between the gateway node and sensors might happen with different protocols: bluetooth, wifi, lora, zigbee.
* besides the gateway node, we need to control every sensor and be able to provision and to power cycle them.
We are pretty confident on running tests on single boards (with and without interaction with LXC containers) but as the above example is more complex we need some guidance on how this can be achieved with LAVA.
The main question mark we have is how LAVA interacts with Cortex-M devices, especially for their deployment.
Does anyone of you have a similar scenario? What are the main challenges? How complicated and/or robust to run something similar with LAVA?
Can you point us to documentation, examples?
Any help is very much appreciated.
Thanks!
--
Diego Russo | Staff Software Engineer | Mbed Linux OS
ARM Ltd. CPC1, Capital Park, Cambridge Road, Fulbourn, CB21 5XE, United Kingdom
http://www.diegor.co.uk - https://os.mbed.com/linux-os/
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hello,
We have some tests that are currently expected to fail, and should then become passes once the implementation of the feature is complete.
Is this something LAVA results can support? As far as I can see the result can be pass/fail/skip (and possibly unknown).
Suggestions welcome.
Thanks.
Pete
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hello,
we are trying to add external interfaces on the worker to connect with the DUTs, for example a 4-port USB-to-RS232 converter. Our DUTs have multiple RS232 ports which shall be tested using this remote interface.
We have already figured out how to integrate this hardware into the LAVA environment, so that it can be used within the LAVA LXC (using static_info in the device dictionary, resulting in the four /dev/ttyUSB* devices being visible there).
First question: We need multiple of these converters attached to the worker. How do we integrate these into LAVA? They all have the same board_id, vendor_id and product_id. If I specify the board_id in the device dictionary multiple times, the device is still added only once.
Second question: We need a way to specify to which of the /dev/ttyUSB* ports a certain RS232 port of the DUT is connected. The place where I would assume to put such information is the device dictionary. But how can we access this information within a LAVA test shell?
The documentation specifies some similar mechanism for energy probes:
https://validation.linaro.org/static/docs/v2/admin-lxc-deploy.html?highligh…
It says "Devices which are not directly attached to the worker can also be supported, for example energy probes which communicate over the network".
As far as I can tell from the code, though, this seems to be a hard-coded feature without any possibility of adding other custom hardware. Is that correct?
If yes, why isn't there a generic mechanism to supply static_info from the device dictionary in the LAVA test shell? Or is there?
How can we implement our scenario described above using LAVA?
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
WE MAKE IT YOURS!
Sitz der Gesellschaft: D-21079 Hamburg
Registergericht: Amtsgericht Hamburg, HRB 60514
Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
