Miloš Prchlík

`Result.original_result` was observed as always being set to `fail`, unexpectedly - it should have been `pass` when only checks failed.

> Hm, the difference in the master socket paths is this: > > ``` > /run/user/12559/tmt-default-0 > /run/user/12559/tmt > ``` > > I guess there might be still collisions across...

It might be some race condition, socket removed or something similar. `provision` does remove them when leaving, and I'm not sure how it interacts with `--last`.

~~I'm afraid it works for me:~~ Nevermind, it does *not* work, and I'm able to reproduce the behavior: ``` (dev) [pts-6:0]: happz@multivac [main] ~/git/tmt $ tmt run provision -h virtual...

I believe it's a "leaked" SSH master process. The first tmt invocation leaves the guest running, and with that, the SSH master process is also up and running. The second...

I'm thinking of adding some kind of "soft cleanup" method to our steps, something that would be called when leaving the step, but it would not be expected to clean...

> I've been playing with ssh on and off for quite some time now and would love to learn your thoughts if any of these are worth pursuing: I don't...

Would it be useful to submit at least an abridged version of the log, with the "too long, had to cut" header? With the proposed code, user gets a note...

Rebased & moved release note where it belongs. In f617cb31, I tried to switch from `int` to `tmt.hardware.Size` which should be the language to use when speaking about amounts of...

Proposed one potential solution in https://github.com/teemtee/tmt/issues/3538#issuecomment-2836372867