Re: [PATCH 4/4] dts: log stderr with failed remote commands

On Fri, Feb 23, 2024 at 8:19 PM Luca Vizzarro wrote: > > On 29/01/2024 13:10, Juraj Linkeš wrote: > > Here's I'd add logged additionally as an error, as this sounds as if > > we're changing debug to error > > That is also a way of doing this, but an error is an error. If we wanted > to log the sam

Re: [PATCH 4/4] dts: log stderr with failed remote commands

On 29/01/2024 13:10, Juraj Linkeš wrote: Here's I'd add logged additionally as an error, as this sounds as if we're changing debug to error That is also a way of doing this, but an error is an error. If we wanted to log the same thing in debug and error, then when we go read the debug we get

Re: [PATCH 4/4] dts: log stderr with failed remote commands

On Mon, Jan 22, 2024 at 7:26 PM Luca Vizzarro wrote: > > Add the executed command stderr to RemoteCommandExecutionError. So that > it is logged as an error, instead of just as debug. Here's I'd add logged additionally as an error, as this sounds as if we're changing debug to error. > > Reviewed-

[PATCH 4/4] dts: log stderr with failed remote commands

Add the executed command stderr to RemoteCommandExecutionError. So that it is logged as an error, instead of just as debug. Reviewed-by: Paul Szczepanek Signed-off-by: Luca Vizzarro --- dts/framework/exception.py | 10 +++--- dts/framework/remote_session/remote_session.p