Hi Tom, On Fri, 1 Nov 2024 at 18:08, Tom Rini <[email protected]> wrote: > > On Fri, Nov 01, 2024 at 04:33:47PM +0100, Simon Glass wrote: > > Hi Tom, > > > > On Thu, 31 Oct 2024 at 19:34, Tom Rini <[email protected]> wrote: > > > > > > On Thu, Oct 31, 2024 at 07:00:14PM +0100, Simon Glass wrote: > > > > Hi Tom, > > > > > > > > On Wed, 30 Oct 2024 at 00:53, Tom Rini <[email protected]> wrote: > > > > > > > > > > On Wed, Oct 09, 2024 at 07:51:36PM -0600, Simon Glass wrote: > > > > > > > > > > > When a board is finished with, the lab may want to power it off, or > > > > > > perform some other function. Add a new script which is called when > > > > > > tests > > > > > > are complete. > > > > > > > > > > > > Signed-off-by: Simon Glass <[email protected]> > > > > > > > > > > Reviewed-by: Tom Rini <[email protected]> > > > > > > > > > > But please note I don't see an up to date version of the > > > > > u-boot-test-hooks side of this which would include the release > > > > > wrapper, > > > > > and presumably files. > > > > > > > > Please see my patch from late August "Provide some basic scripts for > > > > Labgrid integration" > > > > > > Yes. There was quite a long discussion on patch 3/3 and I'm not 100% > > > sure where the next steps there are on what the next iteration should > > > have. If the release script was it's own patch then I believe the first > > > 3 patches could be merged today and then that leaves the actual labgrid > > > stuff that conflicts with my setup to figure out. > > > > I tested my patches with my non-Labgrid setup (pyttest, tbot) and it > > still worked. That's not to say there aren't problems, but I am > > hopeful that it will not affect you. > > I can re-name my scripts to labgrid-trini or whatever, sure. But it > wasn't clear if what you were suggesting was flexible enough in general > for how others setup labs too.
Well I can rename mine to labgrid-sjg if that helps. It makes sense, since we have two ways of operating. Regards, Simon
