March 2022 - CI - Fedora Mailing-Lists

[Fedocal] Reminder meeting : Fedora CI SIG

by jbair＠redhat.com

Dear all, You are kindly invited to the meeting: Fedora CI SIG on 2022-03-23 from 09:30:00 to 10:00:00 America/Chicago At fedora-ci(a)irc.libera.chat The meeting will be about: Fedora CI SIG meeting More information available at: https://fedoraproject.org/wiki/SIGs/CI Introduce projects, discuss issues and plans for the future. Please add topics to discuss into our etherpad: https://etherpad.gnome.org/p/fedora-ci This meeting is recurring for every other Wednesday. Source: https://calendar.fedoraproject.org//meeting/9901/

2 years, 1 month

1
0
0 / 0

Consider keeping the CI diversity, not running Zuul's CI tests on the Testing Farm

by Miro Hrončok

Hello CI folks! Several times somebody asked me "Why there are two CI jobs in Fedora dist-git PRs, when the Zuul's rpm-test and the *Fedora CI - dist-git test* run the exact same tests?" My answers so far was: "I don't know why it happened, but now it works as a nice backup plan. It is very common that one of them breaks [1]. When you see an unreadable infrastructure failure [2] at one of them, you have a pretty good chance tat the other one would still work." With the idea to switch Zuul to the Testing Farm (rpm-tmt-test), this benefit would be lost. We would just have two CI tests runs where both of them have infrastructure failures at the same times (see for example [3]), both of them run on the same system, and both of them run the same tests. Could you please consider not doing that, at least until the overall stability of the CI improves? Thanks, [1] https://pagure.io/fedora-ci/general/issue/44 [2] https://pagure.io/fedora-ci/general/issue/43 [3] https://src.fedoraproject.org/rpms/python-virtualenv/pull-request/59 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 years, 1 month

9
26
0 / 0

My PR test says error ... but where do I find the reason?

by Jan Pazdziora

Hello, I've filed https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/1 attempting to add a CI test to my package. A test Fedora CI - dist-git test got run with result error. The test link on the PR page takes me to https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi... and there I click on Console Output to get to https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi... where I see [Pipeline] echo The status is now "running" [Pipeline] echo Waiting for Testing Farm... [Pipeline] waitForWebhook [Pipeline] retry [Pipeline] { [Pipeline] httpRequest [Pipeline] } [Pipeline] // retry [Pipeline] echo The status is now "error" [Pipeline] } [Pipeline] // script [Pipeline] } Where do I find the actual output of my test to see what went wrong in it? -- Jan Pazdziora Product Owner, Platform Security Readiness, Red Hat

2 years, 1 month

4
4
0 / 0

Fedora 37 gating tests use environment with Fedora 36-signed packages

by Jan Pazdziora

Hello, my Fedora 37 update https://bodhi.fedoraproject.org/updates/FEDORA-2022-ea61708c2d runs a gating test https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi... In the test we check if the tool (rpm2swidtag) generates the correct SWID tags, and one of the things that it checks is the match between the distribution and the signatures used on the packages. However, the output of the gating test shows that the rpm -qi bash | grep '^Signature' command produces + rpm -qi bash + grep '^Signature' Signature : RSA/SHA256, Wed 19 Jan 2022 10:50:42 PM UTC, Key ID 999f7cbf38ab71f4 which is exactly the same that the Fedora 36 job shows in https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi... but it's not the key with which for example the package in the Fedora rawhide container is signed: $ podman run --rm registry.fedoraproject.org/fedora:rawhide rpm -qi bash | grep '^Signature' Signature : RSA/SHA256, Wed Feb 9 02:13:15 2022, Key ID f55ad3fb5323552a Note that the container still has the .fc36 build $ podman run --rm registry.fedoraproject.org/fedora:rawhide rpm -q bash bash-5.1.16-2.fc36.x86_64 but its signature matches the rawhide (and future Fedora 37) key. It seems the environment used to run the tests for Fedora 37 has /etc/os-release which says Fedora 37 but at the same time the packages are not signed with the respective key, even if those signatures are already available as shown by the rawhide compose image. Is this expected or a bug? -- Jan Pazdziora Product Owner, Platform Security Readiness, Red Hat

2 years, 1 month

2
4
0 / 0

[Fedocal] Reminder meeting : Fedora CI SIG

by jbair＠redhat.com

Dear all, You are kindly invited to the meeting: Fedora CI SIG on 2022-03-09 from 09:30:00 to 10:00:00 America/Chicago At fedora-ci(a)irc.libera.chat The meeting will be about: Fedora CI SIG meeting More information available at: https://fedoraproject.org/wiki/SIGs/CI Introduce projects, discuss issues and plans for the future. Please add topics to discuss into our etherpad: https://etherpad.gnome.org/p/fedora-ci This meeting is recurring for every other Wednesday. Source: https://calendar.fedoraproject.org//meeting/9901/

2 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

CI March 2022