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-unpackhttps://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
Hello Philippe,
could you send the raw logs?
Rgds
Le ven. 19 juil. 2019 à 09:34, Philippe BEGNIC philippe.begnic@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@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
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@lists.lavasoftware.org On Behalf Of Remi Duraffort Sent: lundi 22 juillet 2019 17:42 To: Philippe BEGNIC philippe.begnic@st.com Cc: Lava-users@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@st.commailto:philippe.begnic@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-unpackhttps://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@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Team, Linaro
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@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@lists.lavasoftware.org *On Behalf Of *Remi Duraffort *Sent:* lundi 22 juillet 2019 17:42 *To:* Philippe BEGNIC philippe.begnic@st.com *Cc:* Lava-users@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@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@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
--
Rémi Duraffort
LAVA Team, Linaro
Hello everyone,
I am using Lavacli to calculate basic statistics on the daily jobs executed with LAVA. (Nbr of complete//incomplete//canceled jobs). I also display the failure reason of the incomplete and canceled jobs by parsing the jobs logs. I can only do this operation for a limited number of jobs, because it seems that Lavacli has a restriction on the number of jobs to be treated. (100 jobs)
Here the command lines I am using : > lavacli jobs list --health INCOMPLETE --limit 200
To count the number of computed jobs: > lavacli jobs list --health INCOMPLETE --limit 200 |wc -l > 101
So, I have requested 200 jobs, and Lavacli has treated only 100 jobs ( Note that our jobs database contains more than 200 jobs incomplete)
Is it possible to remove or to increase the limitation on the number of jobs to be treated ?
Best regards
Philippe Begnic STMicroelectronics | MDG Group – MCD Division
On 10/22/19 4:16 PM, Philippe BEGNIC wrote: Hello everyone,
I am using Lavacli to calculate basic statistics on the daily jobs executed with LAVA. (Nbr of complete//incomplete//canceled jobs). I also display the failure reason of the incomplete and canceled jobs by parsing the jobs logs. I can only do this operation for a limited number of jobs, because it seems that Lavacli has a restriction on the number of jobs to be treated. (100 jobs)
Here the command lines I am using : > lavacli jobs list --health INCOMPLETE --limit 200
To count the number of computed jobs: > lavacli jobs list --health INCOMPLETE --limit 200 |wc -l > 101
So, I have requested 200 jobs, and Lavacli has treated only 100 jobs ( Note that our jobs database contains more than 200 jobs incomplete)
Is it possible to remove or to increase the limitation on the number of jobs to be treated ?
The lavacli version I am using is lavacli 0.9.5
Best regards
Philippe Begnic STMicroelectronics | MDG Group – MCD Division
_______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Hello,
this is the lava server that limit the number of jobs that will be returned. But the api allows to iterate by setting the "start" parameter. See https://validation.linaro.org/api/help/#scheduler.jobs.list
Rgds
Le mar. 22 oct. 2019 à 16:17, Philippe BEGNIC philippe.begnic@st.com a écrit :
Hello everyone,
I am using Lavacli to calculate basic statistics on the daily jobs executed with LAVA. (Nbr of complete//incomplete//canceled jobs). I also display the failure reason of the incomplete and canceled jobs by parsing the jobs logs. I can only do this operation for a limited number of jobs, because it seems that Lavacli has a restriction on the number of jobs to be treated. (100 jobs)
Here the command lines I am using : > lavacli jobs list --health INCOMPLETE --limit 200
To count the number of computed jobs: > lavacli jobs list --health INCOMPLETE --limit 200 |wc -l > 101
So, I have requested 200 jobs, and Lavacli has treated only 100 jobs ( Note that our jobs database contains more than 200 jobs incomplete)
Is it possible to remove or to increase the limitation on the number of jobs to be treated ?
Best regards
Philippe Begnic STMicroelectronics | MDG Group – MCD Division
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org