Re: [PATCH v2 5/6] test/py: Show info about module-loading

2025-02-17 Thread Tom Rini
On Sat, Feb 15, 2025 at 10:21:43AM -0700, Simon Glass wrote: > Hi Tom, > > On Sat, 15 Feb 2025 at 07:49, Tom Rini wrote: > > > > On Sat, Feb 15, 2025 at 05:17:48AM -0700, Simon Glass wrote: > > > Hi Tom, > > > > > > On Mon, 10 Feb 2025 at 08:52, Tom Rini wrote: > > > > > > > > On Sun, Feb 09, 20

Re: [PATCH v2 5/6] test/py: Show info about module-loading

2025-02-15 Thread Simon Glass
Hi Tom, On Sat, 15 Feb 2025 at 07:49, Tom Rini wrote: > > On Sat, Feb 15, 2025 at 05:17:48AM -0700, Simon Glass wrote: > > Hi Tom, > > > > On Mon, 10 Feb 2025 at 08:52, Tom Rini wrote: > > > > > > On Sun, Feb 09, 2025 at 09:07:18AM -0700, Simon Glass wrote: > > > > > > > It is sometimes tricky t

Re: [PATCH v2 5/6] test/py: Show info about module-loading

2025-02-15 Thread Tom Rini
On Sat, Feb 15, 2025 at 05:17:48AM -0700, Simon Glass wrote: > Hi Tom, > > On Mon, 10 Feb 2025 at 08:52, Tom Rini wrote: > > > > On Sun, Feb 09, 2025 at 09:07:18AM -0700, Simon Glass wrote: > > > > > It is sometimes tricky to figure out what modules test.py is loading > > > when it starts up. The

Re: [PATCH v2 5/6] test/py: Show info about module-loading

2025-02-15 Thread Simon Glass
Hi Tom, On Mon, 10 Feb 2025 at 08:52, Tom Rini wrote: > > On Sun, Feb 09, 2025 at 09:07:18AM -0700, Simon Glass wrote: > > > It is sometimes tricky to figure out what modules test.py is loading > > when it starts up. The result can be a silent failure with no clue as to > > what when wrong. > > >

Re: [PATCH v2 5/6] test/py: Show info about module-loading

2025-02-10 Thread Tom Rini
On Sun, Feb 09, 2025 at 09:07:18AM -0700, Simon Glass wrote: > It is sometimes tricky to figure out what modules test.py is loading > when it starts up. The result can be a silent failure with no clue as to > what when wrong. > > Add a section which lists the modules loaded as well as those not >

[PATCH v2 5/6] test/py: Show info about module-loading

2025-02-09 Thread Simon Glass
It is sometimes tricky to figure out what modules test.py is loading when it starts up. The result can be a silent failure with no clue as to what when wrong. Add a section which lists the modules loaded as well as those not found. Signed-off-by: Simon Glass --- (no changes since v1) test/py/