On Fri, Oct 4, 2019, 17:59 Diego Russo Diego.Russo@arm.com wrote:

Hello,

I have a job with the following flow:

1. deploy the DUT
2. boot the DUT
3. while booting, I need to capture a string: it is the version/timestamp

of BL2. For example: NOTICE: BL2: v2.1(release):v2.1-232-g89a4d26-dirty NOTICE: BL2: Built : 04:06:44, Sep 25 2019

4. perform an update of the BL2
5. reboot the device
6. while booting the second time, I need to capture again the

version/timestamp 7) Compare the 2 strings: if they are different, the test passes.

How can I do 3) 6) and 7) with LAVA?

I don't think it can currently be done in LAVA. Remi, any suggestions?

milosz

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. _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

Hello,

Thanks for your reply. It seems there is a way to get logs of specific jobs (https://docs.lavasoftware.org/lava/results-intro.html#accessing-associated-s...) Can a job access its own logs while executing?

Thanks

From: Remi Duraffort remi.duraffort@linaro.org Date: Monday, 7 October 2019 at 09:50 To: Milosz Wasilewski milosz.wasilewski@linaro.org Cc: Diego Russo Diego.Russo@arm.com, Lava Users Mailman list lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] Comparing output within a job execution between reboots

Hello,

I believe that you should do that outside of lava by post processing the logs. Really easy to do with a small script.

Rgds

Le sam. 5 oct. 2019 à 10:13, Milosz Wasilewski <milosz.wasilewski@linaro.orgmailto:milosz.wasilewski@linaro.org> a écrit :

On Fri, Oct 4, 2019, 17:59 Diego Russo <Diego.Russo@arm.commailto:Diego.Russo@arm.com> wrote: Hello,

I have a job with the following flow: 1) deploy the DUT 2) boot the DUT 3) while booting, I need to capture a string: it is the version/timestamp of BL2. For example: NOTICE: BL2: v2.1(release):v2.1-232-g89a4d26-dirty NOTICE: BL2: Built : 04:06:44, Sep 25 2019

4) perform an update of the BL2 5) reboot the device 6) while booting the second time, I need to capture again the version/timestamp 7) Compare the 2 strings: if they are different, the test passes.

How can I do 3) 6) and 7) with LAVA?

I don't think it can currently be done in LAVA. Remi, any suggestions?

milosz

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. _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

-- Rémi Duraffort LAVA Tech Lead Linaro 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.

On Mon, 14 Oct 2019 at 08:54, Remi Duraffort remi.duraffort@linaro.org wrote:

Hello,

Using xmlrpc calls, you can download the job logs like any users (with the right permissions)

I think Diego's question is a bit different. He asks whether logs are available when the job is still running. TBH I never tried that so I've no idea :)

milosz

Le lun. 14 oct. 2019 à 09:46, Diego Russo Diego.Russo@arm.com a écrit :

...

Hello,

Thanks for your reply. It seems there is a way to get logs of specific jobs (https://docs.lavasoftware.org/lava/results-intro.html#accessing-associated-s...)

Can a job access its own logs while executing?

Thanks

From: Remi Duraffort remi.duraffort@linaro.org Date: Monday, 7 October 2019 at 09:50 To: Milosz Wasilewski milosz.wasilewski@linaro.org Cc: Diego Russo Diego.Russo@arm.com, Lava Users Mailman list lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] Comparing output within a job execution between reboots

Hello,

I believe that you should do that outside of lava by post processing the logs. Really easy to do with a small script.

Rgds

Le sam. 5 oct. 2019 à 10:13, Milosz Wasilewski milosz.wasilewski@linaro.org a écrit :

On Fri, Oct 4, 2019, 17:59 Diego Russo Diego.Russo@arm.com wrote:

Hello,

I have a job with the following flow:

1. deploy the DUT
2. boot the DUT
3. while booting, I need to capture a string: it is the version/timestamp of BL2. For example:

NOTICE: BL2: v2.1(release):v2.1-232-g89a4d26-dirty NOTICE: BL2: Built : 04:06:44, Sep 25 2019

4. perform an update of the BL2
5. reboot the device
6. while booting the second time, I need to capture again the version/timestamp
7. Compare the 2 strings: if they are different, the test passes.

How can I do 3) 6) and 7) with LAVA?

I don't think it can currently be done in LAVA. Remi, any suggestions?

milosz

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. _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

---

Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

--

Rémi Duraffort

LAVA Tech Lead

Linaro

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.

-- Rémi Duraffort LAVA Tech Lead Linaro

Thanks guys,

I guess I have the basis for giving a try.

Cheers From: Remi Duraffort remi.duraffort@linaro.org Date: Monday, 14 October 2019 at 09:17 To: Milosz Wasilewski milosz.wasilewski@linaro.org Cc: Diego Russo Diego.Russo@arm.com, Lava Users Mailman list lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] Comparing output within a job execution between reboots

The logs are streamed from the dispatcher to the server in real time so the logs will be available using the xmlrpc endpoint (unless the network is down) but they are not stored locally by the dispatcher.

Le lun. 14 oct. 2019 à 10:02, Milosz Wasilewski <milosz.wasilewski@linaro.orgmailto:milosz.wasilewski@linaro.org> a écrit : On Mon, 14 Oct 2019 at 08:54, Remi Duraffort <remi.duraffort@linaro.orgmailto:remi.duraffort@linaro.org> wrote:

Hello,

Using xmlrpc calls, you can download the job logs like any users (with the right permissions)

I think Diego's question is a bit different. He asks whether logs are available when the job is still running. TBH I never tried that so I've no idea :)

milosz

Le lun. 14 oct. 2019 à 09:46, Diego Russo <Diego.Russo@arm.commailto:Diego.Russo@arm.com> a écrit :

...

Hello,

Thanks for your reply. It seems there is a way to get logs of specific jobs (https://docs.lavasoftware.org/lava/results-intro.html#accessing-associated-s...)

Can a job access its own logs while executing?

Thanks

From: Remi Duraffort <remi.duraffort@linaro.orgmailto:remi.duraffort@linaro.org> Date: Monday, 7 October 2019 at 09:50 To: Milosz Wasilewski <milosz.wasilewski@linaro.orgmailto:milosz.wasilewski@linaro.org> Cc: Diego Russo <Diego.Russo@arm.commailto:Diego.Russo@arm.com>, Lava Users Mailman list <lava-users@lists.lavasoftware.orgmailto:lava-users@lists.lavasoftware.org> Subject: Re: [Lava-users] Comparing output within a job execution between reboots

Hello,

I believe that you should do that outside of lava by post processing the logs. Really easy to do with a small script.

Rgds

Le sam. 5 oct. 2019 à 10:13, Milosz Wasilewski <milosz.wasilewski@linaro.orgmailto:milosz.wasilewski@linaro.org> a écrit :

On Fri, Oct 4, 2019, 17:59 Diego Russo <Diego.Russo@arm.commailto:Diego.Russo@arm.com> wrote:

Hello,

I have a job with the following flow:

1. deploy the DUT
2. boot the DUT
3. while booting, I need to capture a string: it is the version/timestamp of BL2. For example:

NOTICE: BL2: v2.1(release):v2.1-232-g89a4d26-dirty NOTICE: BL2: Built : 04:06:44, Sep 25 2019

4. perform an update of the BL2
5. reboot the device
6. while booting the second time, I need to capture again the version/timestamp
7. Compare the 2 strings: if they are different, the test passes.

How can I do 3) 6) and 7) with LAVA?

I don't think it can currently be done in LAVA. Remi, any suggestions?

milosz

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. _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

---

Lava-users mailing list Lava-users@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

--

Rémi Duraffort

LAVA Tech Lead

Linaro

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.

-- Rémi Duraffort LAVA Tech Lead Linaro

-- Rémi Duraffort LAVA Tech Lead Linaro 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.