ERROR Unable to find tree root

[hroncok]

[python-virtualenv (py34-patch %)]$ git remote -v
churchyard	ssh://pkgs.fedoraproject.org/forks/churchyard/rpms/python-virtualenv.git (fetch)
churchyard	ssh://pkgs.fedoraproject.org/forks/churchyard/rpms/python-virtualenv.git (push)
origin	ssh://[email protected]/rpms/python-virtualenv (fetch)
origin	ssh://[email protected]/rpms/python-virtualenv (push)
[python-virtualenv (py34-patch %)]$ git branch 
  16.6.1
  master
  nopy2
* py34-patch
  test38
  you_shall_not_pass
[python-virtualenv (py34-patch %)]$ tmt discover
 ERROR  Unable to find tree root for '/home/churchyard/rpmbuild/fedora-scm/python-virtualenv'.

[psss]

This means no config was found. Just enter one of the directories with examples for quick experimenting. The message should say more clearly that no metadata have been found.

[hroncok]

Oh. this is maybe a mismatch of expectations and reality then. i came to test this tool on my package with CI.

[psss]

I see. This is for now just a very early prototype, basically an outline. To start somewhere and give idea of how the command line interface could/would look like. Feel free to comment drafted options/subcommands if something like that would work for you. Also, so far we haven't planned support for the Standard Test Interface. We can consider later to provide some kind of backward-compatibility support as well.

[hroncok]

Can I use the test metadata specification (L1 and L2) to define my Fedora CI tests today?

[psss]

Not yet, but we're getting close. At Flock we've presented a simple prototype for github pull requests with packit integration. Fedora CI and RHEL CI are our next steps where we want to enable this. This library/tool will be part of that.