- lava-devel - op-lists.linaro.org

Get Updated Adobe AD0-E207 Practice Questions and Expert-Verified Answers

by 877hyacinth＠wshu.net

Prepare confidently for the WGU Global-Economics-for-Managers certification exam with professionally designed study resources from Pass4Future. Our updated exam preparation materials are created to help candidates strengthen their knowledge, improve practical understanding, and prepare efficiently for the WGU certification exam. The Global-Economics-for-Managers exam preparation material includes carefully reviewed practice questions, easy-to-follow PDF study guides, and exam-focused content aligned with the latest exam objectives. Each question is evaluated by experienced professionals to ensure quality, accuracy, and relevance for real exam preparation. With structured and reliable learning resources, Pass4Future helps candidates improve confidence, enhance exam readiness, and maximize their chances of success on the first attempt. Download the latest WGU Global-Economics-for-Managers exam preparation material :https://www.pass4future.com/adobe/exam/ad0-e207

1 month, 2 weeks

1
0
0 0

is the docs valided?thanks.

by 16601874595

Hi: Does this document still work? It feels like there are different formats mixed together, dictionary and template, job are inconsistent http://localhost/static/docs/v2/actions-boot.html#password-prompt

10 months, 1 week

2
1
0 0

how to discrib a ssh device?

by 16601874595＠163.com

Device is RAM, directly connected to the FT4232H through JTAG, FT4232T connected to the windows host through USB-MicroUsb, the windows host provides the telnet test command interface to the workers of the lava automated test environment through the telnet server, in this scenario, how to create the device type, device and job in lava, Can you use lava to automate testing of RAM?

10 months, 1 week

2
1
0 0

how to loop "-boot" action for reboot stress test?

by irreallich＠126.com

Because our system needs to save some content when rebooting, I hope to test this function, such as rebooting 5000 times, but I don’t know how to add a loop to lava device (jinja2) or job (yaml). I find the file https://github.com/Linaro/lava-test-plans/blob/master/lava_test_plans/testc…, It looks like the "-boot" action can be controlled through a for loop. {% for index in range(1,8) %} {% with FASTBOOT_COMMANDS=Null %} - boot: {% include "include/boot_target/boot_target.jinja2" %} {% endwith %} {% with test_timeout=boottime_timeout %} {% include "include/test_target.jinja2" %} {% endwith %} But when I try the following code, {% for index in range(1,8) %} - boot: method: minimal timeout: minutes: 10 auto_login: login_prompt: 'tegra-ubuntu login:' username: root password_prompt: "Password:" password: "root" login_commands: - ifconfig prompts: - 'root@tegra-ubuntu:' parameters: kernel-start-message: '' transfer_overlay: download_command: cd /tmp ; wget unpack_command: tar -m -C / -xzf {% endfor %} lava report error: line22 is "{% for index in range(1,8) %}" Invalid definition: Loading job submission failed: while scanning for the next token found character that cannot start any token in "", line 22, column 2. Where did I go wrong? I tried to get help from lava-users(a)lists.lavasoftware.org but never got a reply, link: https://lists.lavasoftware.org/archives/list/lava-users@lists.lavasoftware.…

2 years, 2 months

3
4
0 0

Request to change status of failure retry option:

by pawanKumar

2 years, 2 months

1
0
0 0

Customize job status/ Test case failure:

by pawanKumar

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*

2 years, 4 months

2
5
0 0

Error Message on boot log:

by pawanKumar

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

2 years, 5 months

2
3
0 0

Index out of range error in some LAVA jobs

by Dave Pigott

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

2 years, 12 months

2
2
0 0

Notify User in Lava:

by pawanKumar

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

2 years, 12 months

2
3
0 0

Re: [Lava-users] Re: Pass Enter key press after u-boot:

by pawanKumar

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 > >

3 years, 1 month

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

lava-devel