Hey there!
LAVA documentation at https://validation.linaro.org/static/docs/v2/contribution.html#creating-a-g… describes how to create an account and request fork permissions. Sadly the step to request fork permissions doesn't work as I can't file that requested issue to ask for access as after some days my GitLab account still yields this message at login: »Your account is pending approval from your GitLab administrator and hence blocked. Please contact your GitLab administrator if you think this is an error.« - without explanation on how to contact that administrator.
So how is the process of contributing thought to happen?
Can someone please forward this to that »GitLab administrator« so he can sort this out and get in contact with me?
Thanks in advance
Stefan
Hi All,
I'm looking to automate overall testing process and post the test results
in to JIRA instead of going to Lava CI.
Is there any way that I can use robot framework to run the tests on Lava
and so robot framework produces results in XML file that can be used to
post into issue tracker.
Any suggestions would be helpful
Thanks,
Pavan
Hello Team,
Good Day to All!
We are setting up a new device into LAVA Automation with the following
requirements.
Flash panel to R4 image
Copy delta to R5
Deploy R5
reboot
Make sure the panel boots to R5
The Test definition i'm using is as follows:
actions:
- deploy:
to: flasher
images:
package:
url:
https://artifactory.softwaretools.com/artifactory/mfgtools-***-0v3
- boot:
timeout:
minutes: 15
commands:
- boot
method: u-boot
prompts:
- 'root@hon-grip'
auto_login:
login_prompt: 'login: '
username: root
password_prompt: 'Password:'
password: root
login_commands:
- coredump --enable
- sysinfo
- ifconfig
- networkctl status
- wget http://192.100.**.**/oslat
- ostree static-delta apply-offline /home/root/oslat
- ostree admin deploy
35b3297cf3e4bc59d2a21e2ae9f7a02ef3f7a940e37389a7e9ae66a610c60b7
- reboot
After reboot command is executed, the panel again prompts for login and
password, whereas I cannot declare auto_login for the second time.
Please let me know how to disable auto login after the reboot (for second
time login)
Best Regards
*Pavan Kumar*
Hello Remi,
A while back you gave a presentation [0] on your efforts on a new tool called LAVAPeur.
The project looks like a great idea.
I was just wondering, what is the current status of this work?
[0] https://resources.linaro.org/en/resource/hj6KGw9fnhKVgvXDdE3qAS
Kind regards, Chris
Hi,
I'm facing an issue after updating the base-uboot file on the server.
*Configuration Error: missing or invalid template.*
*Jobs requesting this device type will not be able to start until a
template is available on the master.*
I have restarted the server and dispatcher but no update. All the devices
went offline automatically.
Any advice to resolve this issue would be appreciated.
Thank you
Hi Team,
Good day to you!
I'm making a dispatcher setup to connect new devices and run tests. In
order to do this, I have connected all the required hardware correctly and
created configuration files by following Lava documentation. I Am able to
control the device with the relay board automatically and can login using
telnet.
I'm trying to run my initial test job definition, It downloads the image
but fails to flash the image on device with the below message:
- {"dt": "2022-08-22T09:07:45.799863", "lvl": "debug", "msg": "Calling:
'nice' 'flash' 'pk_raspi-unit1' '{package}'"}
- {"dt": "2022-08-22T09:07:45.809654", "lvl": "debug", "msg": ">>
/var/lib/lava/dispatcher/tmp/466/deploy-flasher-p2k8tvri
/var/lib/lava/dispatcher/tmp/466/deploy-flasher-p2k8tvri\r"}
- {"dt": "2022-08-22T09:07:45.811510", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.811674", "lvl": "debug", "msg": ">> 7-Zip
[64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21\r"}
- {"dt": "2022-08-22T09:07:45.811955", "lvl": "debug", "msg": ">> p7zip
Version 16.02 (locale=C.UTF-8,Utf16=on,HugeFiles=on,64 bits,8 CPUs Intel(R)
Core(TM) i5-8265U CPU @ 1.60GHz (806EB),ASM,AES-NI)\r"}
- {"dt": "2022-08-22T09:07:45.812045", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812121", "lvl": "debug", "msg": ">> Scanning
the drive for archives:\r"}
- {"dt": "2022-08-22T09:07:45.812195", "lvl": "debug", "msg": ">> 0M
Scan\b\b\b\b\b\b\b\b\b \b\b\b\b\b\b\b\b\b\r"}
- {"dt": "2022-08-22T09:07:45.812266", "lvl": "debug", "msg": ">> ERROR: No
more files\r"}
- {"dt": "2022-08-22T09:07:45.812366", "lvl": "debug", "msg": ">>
{package}\r"}
- {"dt": "2022-08-22T09:07:45.812434", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812712", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812790", "lvl": "debug", "msg": ">> \r"}
- {"dt": "2022-08-22T09:07:45.812860", "lvl": "debug", "msg": ">> System
ERROR:\r"}
- {"dt": "2022-08-22T09:07:45.812929", "lvl": "debug", "msg": ">> Unknown
error -2147024872\r"}
- {"dt": "2022-08-22T09:07:45.813221", "lvl": "debug", "msg": "Returned 2
in 0 seconds"}
- {"dt": "2022-08-22T09:07:45.813306", "lvl": "error", "msg": "Unable to
run 'nice' '['flash', 'pk_raspi-unit1', '{package}']'"}
- {"dt": "2022-08-22T09:07:45.813411", "lvl": "exception", "msg": "Unable
to flash the device"}
Any suggestion to overcome the issue would be very helpful.
Attached log file
Best Regards.
Hello Team,
I'm a new bee to the LAVA environment and learning to perform the
automation testing on my DUT.
But my problem is I have my document which performs booting using serial
and run tests. I need your help here to write a definition that calls
script located in dispatcher and timeout till completion of tests in
script. No need to deploy and boot
I have tried writing only 'test' in actions but it is not successful.
Please suggest the best way to approach to execute script from dispatcher.
Thanks in advance.
Hello, I am a user of the lava software package.
For one of the use cases, I need an ipxe bootloader, I tried to use the one
you collected from here https://docs.lavasoftware.org/lava/ipxe.html, but
it does not have download via nfs.
I tried to build a regular ipxe loader, but it is not compatible with lava
due to text colorization. Can you please tell me if it is possible to find
somewhere a patch that was used in the build of the bootloader to remove
the text colorization?
Best regards,
Volga Bogoslovskiy
