CI April 2019

ci@lists.fedoraproject.org

8 participants
3 discussions

Clarify test result reporting in Standard Test Interface
by Petr Šplíchal 15 May '19

15 May '19

Hi! 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 developer/tester). See the following ticket for proposed solution and share your thoughts there: https://pagure.io/fedora-ci/general/issue/18 Thanks. psss...

1 4

Retrying failed gating tests
by Tom Stellard 26 Apr '19

26 Apr '19

Hi, I created an update for the llvm package, and one of its gating tests[1] failed due to what looks like an infrastructure issue. Is there any way to rerun the test? Thanks, Tom [1] https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Pac…

4 5

Fedora Rawhide CI for upstream
by František Šumšal 18 Apr '19

18 Apr '19

Hello, 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[0]. We already have a bunch of CI's (like CentOS CI[1], Travis CI[2], 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[3], 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). Thank you. Frantisek [0] https://github.com/systemd/systemd [1] https://ci.centos.org/computer/systemd-ci-slave01/ [2] https://travis-ci.org/systemd/systemd [3] https://fedoraproject.org/wiki/FedoraAtomicCI/upstream -- GPG key ID: 0xFB738CE27B634E4B

6 9

2024

2023

2022

2021

2020

2019

2018

2017

CI April 2019