Currently the Standard Test Interface does not define how to
distinguish test failure from an infrastructure error. When
ansible playbook is run it usually does some environment
preparation and only then executes tests. Upon a problem
encountered during provisioning or configuration of the test
environment ansible returns non-zero exit code but there is not an
easy way how to detect such error from a successful test execution
of test which failed (returns non-zero exit code as well).
Let's make this part of the specification more clear so that tools
can detect infrastructure errors and report them as such to the
end user. This will help to direct problems (errors versus
failures) to the right audience (infrastructure staff versus
See the following ticket for proposed solution and share your
As we've recently encountered a significant amount of systemd issues on Fedora Rawhide in upstream,
I started playing with an idea of a Fedora Rawhide CI for our upstream systemd repository. We
already have a bunch of CI's (like CentOS CI, Travis CI, etc.), however, none of them
runs Fedora. We used to have a Fedora Rawhide CI, but it was rather a hack around Copr, which
was neither stable nor maintainable.
I know there's already the Fedora CI, but that's only for Fedora packages (from what I know). In this
case we'd need to build & test each GitHub PR. I stumbled upon a Fedora Atomic CI upstream page,
but haven't found any real-world examples anywhere.
I'm not sure if something like this is possible/feasible in current Fedora infrastructure nor who
to contact with such request, so any hints into the right direction would be appreciated (thanks
to Adam Williamson for pointing me to this list).
GPG key ID: 0xFB738CE27B634E4B