Hi Stephen, > FWIW, this violates the original design of the test system. Turning the > board off at the end of the test is a policy decision that not all > use-cases will want,
Wasn't aware that powering OFF the board would not be a preferred choice for certain test cases. Executing python test cases on sandbox or Beaglebone Black with this power-off feature, did not cause me any issues.So,thought this would be a 'good to use' feature in the python test framework.Hence,this patch. As recommended , will use this power-off outside the pytest environment. Thanks , Adarsh On Fri, 28 May 2021 at 03:12, Stephen Warren <swar...@wwwdotorg.org> wrote: > On 5/27/21 2:33 AM, opensource....@gmail.com wrote: > > From: Adarsh Babu Kalepalli <opensource....@gmail.com> > > > > After executing the test-cases from pytest ,the board > > is still powered.Shutting down the board power supply at > > this point ,would keep the board safe. > > FWIW, this violates the original design of the test system. Turning the > board off at the end of the test is a policy decision that not all > use-cases will want, and hence not something that the test system should > mandate. Instead, the intention is for the user to invoke the test > system using a script that does something like: > > 1) Power on board. > 2) Run test. > 3) Power off board. > > See ./doc/develop/py_testing.rst in the U-Boot source for more > background info, or the following URL for an example script: > > https://github.com/swarren/u-boot-ci-scripts/blob/master/test.sh >