Miloš Prchlík

As discussed offline, `print()` will no longer shift the output depending on `shift` or `level` parameters. It will remain focused on the output rather than logging - and logging is...

Another step in the "make tmt CLI nicer", `tmt about hints` will list and print hints known to tmt. Next, we will make hints more verbose, rendered in HTML, and...

See comments in tests and CLI option: ``` cd tests/run/profile/ tmt --root data -vv test export --profile profiles/test/environment.fmf ``` Pull Request Checklist * [ ] implement the feature * [...

Load global config if the local one does not exist

1

Pull Request Checklist * [ ] implement the feature * [ ] write the documentation * [ ] extend the test coverage * [ ] update the specification * [...

Support additions to context made by adjust rules for follow-up rules

2

```yaml adjust: - when: distro == rhel-9 context+: llvm: 19 - when: llvm == 19 ... ``` Since fmf does not recognize `context`, this might need a combined effort of...

See https://github.com/teemtee/tmt/pull/3617#discussion_r2009065304: ``` echo "fedora ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/fedora chmod 0440 /etc/sudoers.d/fedora ``` would be better than changing `/etc/sudoers`.

```yaml adjust: adjust: [] link: link: [] ... ``` There are several such keys, and tmt does not behave consistently when it comes to corner cases. Some `null` values are...

HW requirements, `and`, `or` and expected outcome

4

Imagine following `provision.hardware` setup: ```yaml hardware: or: - disk: - size: >= 20 GiB - size: >= 512 GiB - size: >= 512 GiB - disk: - size: >= 20...

Pass the original node content to adjust decision callback

1

Because I would really like to show the diff between "before" and "after", and callback was getting just one version. ## Checklist * [x] implement the feature

tmt saves several reports - check logs, phase results, etc. - and they should follow a standardized form. There were some differences, some reports did include timestamps, some did not,...