Miloš Prchlík

This one's even better: ```yaml or: - disk: - size: >= 20 GiB - size: >= 512 GiB - disk: - size: >= 20 GiB - size:

> It seems there was no clear outcome here. @happz, is this something we want/need to make clear before merging the hardware helpers? It's not necessary to resolve before merging...

Filed https://github.com/teemtee/fmf/issues/222 for the change, this would need to happen in fmf.

FTR, there is a prototype: https://github.com/teemtee/tmt/pull/3265

@adiosnb hi, is this issue still valid? There is a degree of synchronization implemented in tmt, as described in https://tmt.readthedocs.io/en/stable/guide.html#multihost-testing, and the test-level synchronization is not implemented on purpose, and...

The documentation might be misleading or unclear, but yes, tmt does expect that whatever `script` is set to, is executable.

> > The documentation might be misleading or unclear, but yes, tmt does expect that whatever `script` is set to, it's executable. > > It can be a set to...

> > It can be a set to a shell code as well. See https://tmt.readthedocs.io/en/stable/spec/tests.html#test > > ``` > > script: | > > echo hello world.. > > ```...

Just realized at least some of these would land in `guests.yaml` if https://github.com/teemtee/tmt/pull/1890 gets merged. Architecture would be missing, but we can easily add `$(arch)` output as yet another fact.

I believe this has been implemented some time ago, see `facts` key: ```yaml $ cat /var/tmp/tmt/run-050/plan/mixed/provision/guests.yaml default-0: -OPTIONLESS-FIELDS: - primary_address - topology_address - facts primary-address: 127.0.0.1 topology-address: 127.0.0.1 role: become:...