Hi,
I saw something like "LAVA_HARD_RESET_COMMAND" was added to environment.
Yes, the test action could use this command to reboot the device now, it's useful.
But, after the command sent, the code in container still need to handle something like next: "Expect press any key to continue" "Press any key" "Expect login prompt" "Login" Etc......
But, this exactly the same code what lava have do in a lots of python files located in "lava_dispatcher/actions/boot".
My question is: do you think it's possible for user code in "docker-test-shell" action directly send any command or use any protocol to tell lava code(maybe a listener or something else) to help to do these things, then after done, the user code in docker test shell continue to execute its own stuff?
You know, this could reuse existed lava code as much as possible. I just want to know if you have plan for this? Thanks.
Larry,
On Tue, 25 Aug 2020 at 04:10, Larry Shen larry.shen@nxp.com wrote:
Hi,
I saw something like “LAVA_HARD_RESET_COMMAND” was added to environment.
I think this is a side effect of adding all device dict variables into the test shell environment.
Yes, the test action could use this command to reboot the device now, it’s useful.
But, after the command sent, the code in container still need to handle something like next:
“Expect press any key to continue”
“Press any key”
“Expect login prompt”
“Login”
Etc……
But, this exactly the same code what lava have do in a lots of python files located in “lava_dispatcher/actions/boot”.
My question is: do you think it’s possible for user code in “docker-test-shell” action directly send any command or use any protocol to tell lava code(maybe a listener or something else) to help to do these things, then after done, the user code in docker test shell continue to execute its own stuff?
My simple answer is: there is no plan about it. If you think this could be a useful feature, please report a ticket in our gitlab so we can discuss the details there. The only place we allow for reboot during the test right now is when running Android CTS. This requires some additional script to look for fastboot devices and run 'fastboot boot'. It's done inside a test: https://github.com/Linaro/test-definitions/blob/master/automated/android/tra...
milosz
You know, this could reuse existed lava code as much as possible. I just want to know if you have plan for this? Thanks.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Hi, Milosz, ticket in https://git.lavasoftware.org/lava/lava/-/issues/434 , thanks.
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Tuesday, August 25, 2020 4:06 PM To: Larry Shen larry.shen@nxp.com Cc: lava-users@lists.lavasoftware.org Subject: [EXT] Re: [Lava-users] Ask plan for docker test shell.
Caution: EXT Email
Larry,
On Tue, 25 Aug 2020 at 04:10, Larry Shen larry.shen@nxp.com wrote:
Hi,
I saw something like “LAVA_HARD_RESET_COMMAND” was added to environment.
I think this is a side effect of adding all device dict variables into the test shell environment.
Yes, the test action could use this command to reboot the device now, it’s useful.
But, after the command sent, the code in container still need to handle something like next:
“Expect press any key to continue”
“Press any key”
“Expect login prompt”
“Login”
Etc……
But, this exactly the same code what lava have do in a lots of python files located in “lava_dispatcher/actions/boot”.
My question is: do you think it’s possible for user code in “docker-test-shell” action directly send any command or use any protocol to tell lava code(maybe a listener or something else) to help to do these things, then after done, the user code in docker test shell continue to execute its own stuff?
My simple answer is: there is no plan about it. If you think this could be a useful feature, please report a ticket in our gitlab so we can discuss the details there. The only place we allow for reboot during the test right now is when running Android CTS. This requires some additional script to look for fastboot devices and run 'fastboot boot'. It's done inside a test: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com...
milosz
You know, this could reuse existed lava code as much as possible. I just want to know if you have plan for this? Thanks.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist s.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01% 7Clarry.shen%40nxp.com%7C0a3119061372456f047608d848cdaa1f%7C686ea1d3bc 2b4c6fa92cd99c5c301635%7C0%7C0%7C637339395445099413&sdata=GvLtRfEP smG4qY5YFNYZTfexM31Kw67ReBprYKa3iCA%3D&reserved=0
lava-users@lists.lavasoftware.org
-
Larry Shen -
Milosz Wasilewski