CI October 2018

ci@lists.fedoraproject.org

2 participants
5 discussions

Fedora CI Metadata Specification moved to Pagure
by Petr Šplíchal 22 Oct '18

22 Oct '18

Hi! In order to make it easier to propose/discuss new (and also existing) attributes we've moved the Fedora CI Metadata specification from wiki to a separate Pagure project here: https://pagure.io/fedora-ci/metadata Two new atttributes related to disabling selected tests and result interpretation have been proposed and are ready for review: https://pagure.io/fedora-ci/metadata/pull-request/1 https://pagure.io/fedora-ci/metadata/pull-request/2 Feedback is welcome. psss...

1 0

Re: Running a test from dist-git
by Petr Šplíchal 15 Oct '18

15 Oct '18

On Thu, 11 Oct 2018 at 09:49, Richard W.M. Jones <rjones(a)redhat.com> wrote: > > On Wed, Oct 10, 2018 at 11:26:01PM +0200, Miroslav Vadkerti wrote: > > Hi, > > > > sorry for the late response :( > > > > On Tue, Oct 2, 2018 at 9:42 AM Richard W.M. Jones <rjones(a)redhat.com> wrote: > > > > > On Mon, Oct 01, 2018 at 11:26:59AM +0200, Miroslav Vadkerti wrote: > > > > For this time I rescheduled the run: > > > > > > > > > > > > > > > https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenk… > > > > > > It appears to have failed, but I've got no clue why. How do I see > > > the output of the command? > > > > > > > Ugh, logs are now gone. Which package were you testing? We can take a look > > what was the problem. > > https://src.fedoraproject.org/rpms/libguestfs > > The test is to run a single command (libguestfs-test-tool). This > command is already installed by the package, so there's no need for > any test harness or script. If the command fails (ie. exit code != 0) > then it's vital we see the complete output in order to diagnose the > problem. > > https://src.fedoraproject.org/rpms/libguestfs/blob/master/f/tests/tests.yml I've created pull request with fixed tests.yml file: https://src.fedoraproject.org/rpms/libguestfs/pull-request/4 In the pull request you would directly see link to the test results including the complete output of the test. Unfortunately there is currently issue with propagating results to Pagure: https://pagure.io/fedora-ci/general/issue/10 We are currently looking into this, it should be fixed soon. Meanwhile it's still possible to see results of the pipeline here: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenk… https://fedoraproject.org/wiki/CI/Pipeline#Instances The latest libguestfs job is this: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenk… Test output can be found under that "Artifact" tab: https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-p… Hope this helps. psss... > Ideally we'd want to run the test as root and non-root, but for now I > just had it run the test as root. > > > > I think it would be easier if we could just drop a shell script into > > > tests/ and have it run that and display the output. The current > > > system seems elaborately overengineered and I don't understand why. > > > > > > > Well, it was decided that we will use Ansible to wrap around our tests. Not > > my idea. I agree the results could be presented better though, even if the > > runner is Ansbile. We are preparing a dashboard to view the result of > > testing, to give a better user experience in the future. > > It wasn't very obvious to start off with, but it seems as if the > "standard test roles" are designed for the simple case of "just run a > script". However the use of YAML combined with the fact that you > can't easily run a test locally makes the whole thing very awkward. > (Also for some reason I didn't investigate yet, my copy of emacs > appears to hate YAML.) > > > If the pipeline goes through (i.e. tests were run), the pipeline ends up > > with Pass (test passed) or Unstable state (tests failed). If the test > > failed, the pipeline did not execute the testing. In the former case you > > should find logs in the Artifacts tab in Jenkins (test results are prefixed > > with PASS_ or FAIL_). If you encounter an error, we are here to help an > > investigate. > > Do the tests run if we submit scratch builds? AFAIK, testing on scratch builds is not currently enabled. > > Anyway feel free to submit a new build of libguestfs if you want to > see if you can make the test run. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-builder quickly builds VMs from scratch > http://libguestfs.org/virt-builder.1.html > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

1 0

Re: Running a test from dist-git
by Miroslav Vadkerti 10 Oct '18

10 Oct '18

Hi, sorry for the late response :( On Tue, Oct 2, 2018 at 9:42 AM Richard W.M. Jones <rjones(a)redhat.com> wrote: > On Mon, Oct 01, 2018 at 11:26:59AM +0200, Miroslav Vadkerti wrote: > > For this time I rescheduled the run: > > > > > > > https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenk… > > It appears to have failed, but I've got no clue why. How do I see > the output of the command? > Ugh, logs are now gone. Which package were you testing? We can take a look what was the problem. > > I think it would be easier if we could just drop a shell script into > tests/ and have it run that and display the output. The current > system seems elaborately overengineered and I don't understand why. > Well, it was decided that we will use Ansible to wrap around our tests. Not my idea. I agree the results could be presented better though, even if the runner is Ansbile. We are preparing a dashboard to view the result of testing, to give a better user experience in the future. If the pipeline goes through (i.e. tests were run), the pipeline ends up with Pass (test passed) or Unstable state (tests failed). If the test failed, the pipeline did not execute the testing. In the former case you should find logs in the Artifacts tab in Jenkins (test results are prefixed with PASS_ or FAIL_). If you encounter an error, we are here to help an investigate. HTH, /M > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-top is 'top' for virtual machines. Tiny program with many > powerful monitoring features, net stats, disk stats, logging, etc. > http://people.redhat.com/~rjones/virt-top > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Miroslav Vadkerti :: Principal QE :: BaseOS QE Security IRC mvadkert #osci #baseosci #qe :: GPG 0x7B5B2E95 Desk Phone +420 532 294 129 :: Mobile +420 773 944 252 Red Hat Czech s.r.o, Purkyňova 99/71, 612 00, Brno, CR

1 0

Flexible Metadata Format: fmf-0.6 released
by Petr Šplíchal 09 Oct '18

09 Oct '18

Hi! New version of the fmf has been released. Contains several fixes related to handling hierarchy and exploring subdirectories, adds support for direct deep dictionary value retrieval and includes some more bugfixes and enhancements: https://github.com/psss/fmf/releases/tag/0.6 Available for experimenting in pip, copr and fedora (testing): https://fmf.readthedocs.io/en/latest/overview.html#install Recently a basic test filtering support using fmf has been added to Standard Test Roles so it's no more necessary to list relevant tests manually. Have a look at the documented real-life examples to see how this works: https://fedoraproject.org/wiki/CI/Examples#Shell https://fedoraproject.org/wiki/CI/Examples#SELinux To learn more about fmf and proposed CI metadata see: https://fedoraproject.org/wiki/Flexible_Metadata_Format https://fedoraproject.org/wiki/CI/Metadata Comments, questions, suggestions welcome. psss...

1 0

Re: Running a test from dist-git
by Miroslav Vadkerti 01 Oct '18

01 Oct '18

Hi, On Thu, Sep 27, 2018 at 11:32 PM Richard W.M. Jones <rjones(a)redhat.com> wrote: > As directed by: > > https://fedoraproject.org/wiki/CI/Tests > > I tried to add a test to libguestfs dist-git: > > > https://src.fedoraproject.org/rpms/libguestfs/blob/master/f/tests/tests.yml > > It's very simple initially. It just needs to run > ‘libguestfs-test-tool’ (a program installed by the libguestfs package > which does some self-tests). Ideally as non-root, but I think I've > set it up to run as root to start with. > Cool :) > > I did a scratch build initially, but it seems like the tests only run > from what's been pushed to dist-git. That is correct. Tests are not bundled into the src.rpm. > In any case the test didn't look > as if it had run. So I pushed the test to dist-git -- see above -- > and did another scratch build. However I've still no real idea if the > test really ran. > > I got an email containing this link: > > > https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenk… Nice, seems fedora notifications works again :) > > > which looks like there are lots of failures, but it's also not clear > if the test ran / tried to run / didn't run / if this link has nothing > to do tests. > Yeah, sorry for that, must have been som outage. I agree seeing that is not very helpful, to somebody not experienced in the CI pipeline. Also rescheduling anything else as a pull-request testing is not easily possible currently :( In the future this should be possible via fedpkg. > > So, that was the end of my experiment. Not a very good result :-( > For this time I rescheduled the run: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenk… Seems it will end up with something more meaningful this time ... HTH, /M > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > libguestfs lets you edit virtual machines. Supports shell scripting, > bindings from many languages. http://libguestfs.org > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Miroslav Vadkerti :: Principal QE :: BaseOS QE Security IRC mvadkert #osci #baseosci #qe :: GPG 0x7B5B2E95 Desk Phone +420 532 294 129 :: Mobile +420 773 944 252 Red Hat Czech s.r.o, Purkyňova 99/71, 612 00, Brno, CR

1 0

2024

2023

2022

2021

2020

2019

2018

2017

CI October 2018