Hi Team,
I was running the lava jobs and I found a difference in the status after
job completion with failures. There were failures in
i) The interactive test and lava overlay test [cases] but still the status
of the job shows as "COMPLETE".
ii) I tried an action failure retry, when action failure for the
first time, it shows the result as failure but job status as complete. The
retry- failure status should be ignored if it fails for the first time. I
convert the test results into JUNIT using rest api. In the junit result it
displays failure for the test case.
My question is, How can we customize the status of the job or ignore the
test result in case of failure-retry?
Any Advice please.
Best Regards
*Pavan Kumar*
Hello Team,
I was trying to flash a binary on the device and run the tests on the
device by using lava overlay.
Board flashes successfully but while booting the device in the boot log
there is a word "*** Invalid partition 3 ***" lava catches the key word
and throws an error message.
For the other devices it is not catching this error with the same boot log.
Only on one device I'm observing this issue.
Please let me know How to ignore the keyword and move on to run the tests.
matched a bootloader error message: 'Invalid partition' (17)
boot log:
*U-Boot SPL 2022.04 (Nov 30 2023 - 20:10:15
+0000)power_bd71837_initDDRINFO: start DRAM initDDRINFO: DRAM rate
1600MTSDDRINFO:ddrphy calibration doneDDRINFO: ddrmix config doneNormal
BootTrying to boot from MMC1hab fuse not enabledAuthenticate image from DDR
location 0x401fcdc0...NOTICE: BL31:
v2.6(release):lf-5.15.32-2.0.0-0-gc6a19b1a3-dirtyNOTICE: BL31: Built :
06:37:22, Jun 7 2022U-Boot 2022.04 (Nov 30 2023 - 20:10:15 +0000)CPU:
i.MX8MMD rev1.0 1600 MHz (running at 1200 MHz)CPU: Industrial temperature
grade (-40C to 105C) at 44CReset cause: PORModel: DRAM: 224
MiBboard_initCore: 61 devices, 21 uclasses, devicetree: separateMMC:
FSL_SDHC: 0Loading Environment from nowhere... OKIn: serialOut:
serialErr: serialSEC0: RNG instantiated BuildInfo: - ATF c6a19b1facmod
value is 1!pulse number is 0�flash target is MMC:0Fastboot: NormalNormal
BootHit any key to stop autoboot: 2 end: 3.4.2 bootloader-interrupt
(duration 00:00:05) [common]start: 3.4.3 bootloader-commands (timeout
00:02:52) [common]Setting prompt string to ['=>']bootloader-commands: Wait
for prompt ['=>'] (timeout 00:02:52) 0 Setting prompt string to
['=>']Sending with 5 millisecond of delaysetenv factorymode 1u-boot=>
setenv factorymode 1bootloader-commands: Wait for prompt ['=>'] (timeout
00:02:51)setenv factorymode 1Sending with 5 millisecond of
delaybootu-boot=> bootboot** Invalid partition 3 **Couldn't find partition
mmc 0:3Can't set block deviceuEnv not found in mmcpart3, checking
mmcpart1Failed to load '/boot/system/uEnv'uEnv not found in mmcpart 1
either!Booting from mmc ...## Error: \"w\" not definedmatched a bootloader
error message: 'Invalid partition' (17)end: 3.4.3 bootloader-commands
(duration 00:00:02) [common]case: bootloader-commandscase_id:
204071definition: lavaduration: 1.52extra: ...level: 3.4.3namespace:
commonresult: fail*
Best Regards
Pavan Kumar
Hi all,
We've been noticing an increase in a particular error, reported as a
lava bug by lava itself. An example job is
https://lava.collabora.dev/scheduler/job/10987740 - however, for
contrast, the following job, which is based on the same template,
succeeds https://lava.collabora.dev/scheduler/job/11017230.
Is this genuinely a LAVA bug or do we have a job definition problem?
Thanks
Dave
--
Dave Pigott
Principal Engineer
Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718
Hello Team,
I'm using notify action in the job definition to notify users about the
status of the job. I'm already a registered user in lava and after
completion of my job, the administration site shows the status as "*not
sent*".
Please let me know what can be the reason, and how can i achieve it?
[image: lava-notify.PNG]
Below is the job definition i'm using:
*device_type: ADT-UNIT1job_name: sample test to notify usertimeouts: job:
minutes: 15 action: minutes: 10 connection: minutes: 5visibility:
publicactions:- command: name: relay_pwr_on timeout:
minutes: 1- deploy: to: flasher images: package:
url:
https://artifactory.softwaretools.com/artifactory/gop-generic-stable-local/…
<https://artifactory.softwaretools.com/artifactory/gop-generic-stable-local/…>-
boot: method: u-boot commands: - setenv factorymode 1 -
boot auto_login: login_prompt: 'login:' username: root
password_prompt: 'Password:' password: root login_commands:
- touch /home/root/test_file - ifconfig prompts: -
'root@hon-grip' - 'root@GRIP'notify: recipients: - to: method:
email user: pavan criteria: status: finished verbosity: verbose*
Thanks & Regards,
Pavan
Hi
Can anyone have a look at the log and suggest what can be done?
Thanks & Regards
*Pavan Kumar*
On Sun, May 21, 2023 at 1:18 PM pawanKumar <pawan4749(a)gmail.com> wrote:
> Hi All,
>
> Thanks for your reply!
>
> I have pasted the log in the link below
> https://pastebin.com/qquMLthi
>
> After the boot completion I have to press "enter" manually to see the
> login prompt. If didn't press any key then it gets disconnected after some
> time. That's how the device is designed.
> By using the job definition it Enter to u-boot and send boot command
> successfully but fails while login as it doesn't see any login prompt.
> Any one please check the log and suggest whether need to make any changes
> in base file or base-uboot file.
> Since it's a new device connecting to existing lava setup I was confused a
> bit.
>
>
>
> Thanks
> *Pavan Kumar*
>
> Show quoted text
>
>
> On Thu, 18 May, 2023, 11:23 am Stefan, <
> lists.lavasoftware.org_23(a)green-sparklet.de> wrote:
>
>> Hi Pavan,
>>
>> if there's really no difference, then you are not using the correct
>> string. Is the prompt really "press enter", or might it be that it is like
>> "Press ENTER to activate this console" or "Please press Enter to activate
>> this console"? That's a difference. You need to use a string that your
>> device really displays on console.
>>
>> Regards
>> Stefan
>>
>> On 2023-05-18 07:30, pawanKumar wrote:
>>
>> Hi Stefan,
>>
>> Did you mean
>> auto_login:
>> login_prompt: "press enter"
>>
>> I tried it but there is no difference, it results in the same error.
>> Any suggestions?
>>
>> Best Regards
>> *Pavan Kumar*
>>
>>
>> On Wed, May 17, 2023 at 10:58 AM Stefan <
>> lists.lavasoftware.org_23(a)green-sparklet.de> wrote:
>>
>>> Hi Pavan,
>>>
>>> what happens if you set the 'login_prompt' to (parts of) that "press
>>> enter" string?
>>> Sure it doesn't work currently, because the string you configured
>>> doesn't get displayed
>>>
>>> Stefan
>>>
>>>
>>> Am 17. Mai 2023 07:00:31 MESZ schrieb pawanKumar <pawan4749(a)gmail.com>:
>>>
>>>> Hi
>>>>
>>>> The auto-login feature is not working here, job is failing with "*wait
>>>> for Prompt timed out*".
>>>> As I mentioned in a previous email, after completion the log login
>>>> prompt is not displayed automatically and you need to press enter key to
>>>> see the login prompt.
>>>>
>>>> Below is the definition I'm using:
>>>>
>>>> device_type: DEVICE-TYPE1
>>>> job_name: boot the device
>>>> timeouts:
>>>> job:
>>>> minutes: 15
>>>> action:
>>>> minutes: 10
>>>> connection:
>>>> minutes: 5
>>>> visibility: public
>>>> actions:
>>>> - command:
>>>> name: relay_pwr_on
>>>> timeout:
>>>> minutes: 1
>>>> - boot:
>>>> method: u-boot
>>>> commands:
>>>> - boot
>>>> auto_login:
>>>> login_prompt: 'rezi-703683 login:'
>>>> username: root
>>>> login_commands:
>>>> - touch /home/root/test_file
>>>> - ifconfig band0
>>>> - cat /etc/os-release
>>>> prompts:
>>>> - 'root@rezi'
>>>> - '#'
>>>> [image: prompt-timeout.PNG]
>>>> Best Regards
>>>> *Pavan Kumar*
>>>>
>>>>
>>>> On Tue, May 16, 2023 at 12:53 PM Remi Duraffort <
>>>> remi.duraffort(a)linaro.org> wrote:
>>>>
>>>>>
>>>>>
>>>>> Le lun. 15 mai 2023 à 11:32, pawanKumar <pawan4749(a)gmail.com> a
>>>>> écrit :
>>>>>
>>>>>> Hi Stefan,
>>>>>>
>>>>>> It means after the boot process completion, i should press "enter"
>>>>>> then only it displays a login prompt to pass username then enters into the
>>>>>> system.
>>>>>>
>>>>>
>>>>> As answered by stefan, using auto-login feature should work.
>>>>>
>>>>>
>>>>>>
>>>>>> Please check the attachment.
>>>>>>
>>>>>>
>>>>>> Best Regards
>>>>>> *Pavan Kumar*
>>>>>>
>>>>>>
>>>>>> On Mon, May 15, 2023 at 1:22 PM Stefan <
>>>>>> lists.lavasoftware.org_23(a)green-sparklet.de> wrote:
>>>>>>
>>>>>>> Hey Pavan kumar,
>>>>>>>
>>>>>>> what do mean by "after U-Boot process completion"? What does your
>>>>>>> config look like? Are you still in U-Boot, or did you already boot up your
>>>>>>> system?
>>>>>>>
>>>>>>> For the first one, it would help to modify |'||base_uboot_bootcmd'
>>>>>>> which can be overridden in your device template.
>>>>>>>
>>>>>>> If your system is already booted up, it would be up to auto_login <
>>>>>>> https://docs.lavasoftware.org/lava/actions-boot.html#auto-login> to
>>>>>>> be configured properly and take over.
>>>>>>>
>>>>>>> Regards
>>>>>>> Stefan
>>>>>>> |
>>>>>>> On 5/15/2023 9:29 AM, pawanKumar wrote:
>>>>>>> > Hello Team,
>>>>>>> >
>>>>>>> > Good Day to you!
>>>>>>> >
>>>>>>> > I have a requirement to pass "enter" key after u-boot process
>>>>>>> completion, to enter into the system.
>>>>>>> > Without pressing any key cannot enter into prompt and it stays
>>>>>>> stagnant.
>>>>>>> >
>>>>>>> > Please let me know how to pass "enter" press key at the end of
>>>>>>> u-boot log.
>>>>>>> >
>>>>>>> >
>>>>>>> > Thanks
>>>>>>> > Pavan kumar
>>>>>>> >
>>>>>>> > _______________________________________________
>>>>>>> > Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>>>>>> > To unsubscribe send an email to
>>>>>>> lava-users-leave(a)lists.lavasoftware.org
>>>>>>> > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>>>>>> To unsubscribe send an email to
>>>>>>> lava-users-leave(a)lists.lavasoftware.org
>>>>>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>>
>>>>>> _______________________________________________
>>>>>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>>>>> To unsubscribe send an email to
>>>>>> lava-users-leave(a)lists.lavasoftware.org
>>>>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Rémi Duraffort
>>>>> Principal Tech Lead
>>>>> Automation Software Team
>>>>> Linaro
>>>>>
>>>> _______________________________________________
>>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>>> To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>
>>
>> _______________________________________________
>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>> To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>
>>
>> _______________________________________________
>> Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
>> To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
>
Hello Team,
Good Day to you!
I have a requirement to pass "enter" key after u-boot process completion,
to enter into the system.
Without pressing any key cannot enter into prompt and it stays stagnant.
Please let me know how to pass "enter" press key at the end of u-boot log.
Thanks
Pavan kumar
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*
