Miroslav Vadkerti
Miroslav Vadkerti
> @thrix please, take a look at tests, there is some red color reported. yeah, looking, thx
/packit retest-failed
> The `/tests/report/interrupted` test was [failing](https://artifacts.osci.redhat.com/testing-farm/378a1f1f-3d81-4afa-9481-07839fa1aa95/work-the-rest85y5_oc0/plans/provision/virtual/the-rest/execute/data/guest/default-0/tests/report/interrupted-11/output.txt) because it did not expect `error` in the report summary. This is expected and should be fixed by [6e9aea3](https://github.com/teemtee/tmt/commit/6e9aea394349af9d45eeedf320ac4026930f91cd). thanks for fixing it
/packit propose-downstream
yeah, makes sense to me, currently I do not see any problems doing that
Would be nice to unify somehow the directory structure for saving such data, feels a bit like rpms, maybe other artifacts needed by other steps could share this unified space...
@pvalena did not think about that (make example) I guess that makes sense, feels dangerous! Thanks @pvalena So I take my good idea of this back ... @psss seems this...
@psss I guess that can be part of #423 also ... seems I will be a bit area also there
> So, how to proceed to make it as painless for the end user as possible? Do we know who out there consumes `results.yaml`? I am fine introducing the breaking...
> > So, how to proceed to make it as painless for the end user as possible? Do we know who out there consumes `results.yaml`? > > I am fine...