- CI - Fedora mailing-lists

[release] Testing Farm 2024-04.4
by Jan Havlin 27 Jun '24

27 Jun '24

Testing Farm hotpatch 2024-04.4 with tmt 1.34 has been released! *Changes* tmt was updated from 1.33 to 1.34 <https://tmt.readthedocs.io/en/stable/releases.html#tmt-1-34>. tmt process now accepts more environment variables regarding Reportportal ( infrastructure!632 <https://gitlab.com/testing-farm/infrastructure/-/merge_requests/632>). *Packages* List of important packages bundled in the worker image: ❯ podman run --entrypoint rpm quay.io/testing-farm/worker-public:2024-04.4 -q tmt standard-test-roles ansible-core podman beakerlib | sort | uniq ansible-core-2.16.7-1.fc40.noarch beakerlib-1.29.3-5.fc40.noarch podman-5.1.1-1.fc40.x86_64 standard-test-roles-4.11-3.fc40.noarch tmt-1.34.0-1.fc40.noarch The next Testing Farm release will be 2024-07.1. On behalf of the Testing Farm Team Jan Havlin

1 0

Fedora Rawhide PR CI broken for a week, please fix
by Miro Hrončok 19 Jun '24

19 Jun '24

Hi, since we merged the Python 3.13 side tag, the CI on Fedora Rawhide PRs seems borked. https://pagure.io/fedora-ci/general/issue/474 Can somebody please take a look? It has been a week. I can help if the issue is related to Python itself, but this is extremely impossible for me to debug. -- Miro Hrončok -- Phone: +420777974800 Fedora Matrix: mhroncok

1 0

TMT multihost testing support
by Jan Staněk 19 Jun '24

19 Jun '24

Hello list! Is multihost TMT testing supported by Fedora CI? Are there any plans and/or guides covering it? I have a component (nodejs-undici) that makes network calls; I would like to have a separate container running (serving something similar to https://httpbin.org) that would be available during the test run and could respond to network requests from the main testing container. Thanks in advance for any answers! -- Jan Staněk Software Engineer, Red Hat jstanek(a)redhat.com irc: jstanek

2 2

Software Factory Services Outage fedora.softwarefactory-project.io: 2024-06-11 and 2024-06-24 at 13:00 UTC
by Tristan Cacqueray 29 May '24

29 May '24

Hello, The Production Chain Infra Team is planning to do the following services maintainances: - Upgrade Zuul and Gerrit to the latest versions on the 2024-06-11 - Upgrade the control plane operating systems from CentOS 7 to RHEL 9 on the 2024-06-24. During these maintainances, the following services are going to be unavailable for a few hours: - Zuul CI not running jobs for pagure.io or src.fedoraproject.org. Please let us know if the proposed windows are not good for you. Regards, Tristan, on behalf of the Software Factory Operation Team

1 0

[release] Testing Farm 2024-04.1
by Evgeny Fedin 10 May '24

10 May '24

Hi, Testing Farm release 2024-04.1 is deployed 🎉. <#user-content-upgrades>🚀 Upgrades Testing Farm CLI </testing-farm/docs/root/-/blob/b2f32dd2f0d8962eec369a2acff2d3c7e34200de/cli.adoc> tool updated from v0.0.16 to v0.0.17 <https://gitlab.com/testing-farm/cli/-/releases/v0.0.17>, please update your installation. Artemis <https://gitlab.com/testing-farm/artemis/> was updated to v0.0.69 <https://gitlab.com/testing-farm/artemis/-/releases/v0.0.69> on both ranches. tmt was updated from 1.31 to 1.33 <https://tmt.readthedocs.io/en/stable/releases.html#tmt-1-33> (see also release notes for 1.32 <https://tmt.readthedocs.io/en/stable/releases.html#tmt-1-33>) <#user-content-highlights>🎯 Highlights Public ranch supports bare metal instances in AWS - (TFT-702 <https://issues.redhat.com/browse/TFT-702>) Testing Farm workers are connected to monitoring - (TFT-2168 <https://issues.redhat.com/browse/TFT-2168>) The Results Viewer <https://docs.testing-farm.io/Testing%20Farm/0.1/test-results.html#_results_…> now displays artifacts for pipelines that are still running - (TFT-2476 <https://issues.redhat.com/browse/TFT-2476>) Testing Farm CLI allows for longer reserve time up to 72 hours - (TFT-2259 <https://issues.redhat.com/browse/TFT-2259>) Special characters were removed from pipeline.log - (TFT-2406 <https://issues.redhat.com/browse/TFT-2406>) Results Viewer <https://docs.testing-farm.io/Testing%20Farm/0.1/test-results.html#_results_…> displays links to test and plan data directory - (TFT-2437 <https://issues.redhat.com/browse/TFT-2437>) <#user-content-bugfixes>🐞 Bugfixes Fixed performance and logging issues - (TFT-2495 <https://issues.redhat.com/browse/TFT-2495>) Fixed race condition when generating results - (TFT-2493 <https://issues.redhat.com/browse/TFT-2493>) Fixed silently ignored artifact installation failures - (TFT-2494 <https://issues.redhat.com/browse/TFT-2494>) Fixed leaked secrets when invalid payload is sent to Testing Farm API - ( TFT-2485 <https://issues.redhat.com/browse/TFT-2485>) Fixed DNS issues in one of the two concurring test execution - (TFT-2560 <https://issues.redhat.com/browse/TFT-2560>) Fixed UEFI requests are always routed to Beaker - (TFT-2341 <https://issues.redhat.com/browse/TFT-2341>) Testing Farm fails nicely when custom results.yml contains invalid duration - (TFT-2436 <https://issues.redhat.com/browse/TFT-2436>) A newline in a secret value caused secrets to be leaked - (TFT-2468 <https://issues.redhat.com/browse/TFT-2468>) Fixed ignored provision timeout value from Testing Farm API - (TFT-2492 <https://issues.redhat.com/browse/TFT-2492>) Support for zcrypt.adapter and zcrypt.mode hardware requirements - (TFT-2457 <https://issues.redhat.com/browse/TFT-2457>) <#user-content-%EF%B8%8F-packages>📦️ Packages List of important packages bundled in the worker image. ❯ podman run --entrypoint rpm quay.io/testing-farm/worker-public:2024-04.1 -q tmt standard-test-roles ansible-core podman beakerlib | sort | uniqansible-core-2.14.11-2.fc38.noarchbeakerlib-1.29.3-2.fc38.noarchpodman-4.9.4-1.fc38.x86_64standard-test-roles-4.11-2.fc38.noarchtmt-1.33.0-1.fc38.noarch <#user-content-stats>🔎 Stats Testing Farm is on track to surpass 1.12M requests per year <https://stats.testing-farm.io/d/dpYooDIVk/testing-farm-all-time-stats> \o/. The error rate for Testing Farm in April was approximately 3.55% <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?orgId=1&from=171192…> . Around 107k testing requests <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?viewPanel=8&orgId=1…> were recorded in April. The average queue time in February was 3.20 minutes on the Public ranch <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?viewPanel=26&orgId=…> and 16 minutes on the Red Hat ranch <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?viewPanel=27&orgId=…> . On behalf of the Testing Farm Team, -- Evgeny Fedin Senior Software Quality Engineer Red Hat <https://www.redhat.com> efedin(a)redhat.com On slack: @efedin, #testing-farm <https://www.redhat.com>

1 0

Heads up: Fedora CI appears to be borked
by Adam Williamson 09 May '24

09 May '24

It looks to me like all tests in Fedora CI are currently failing. I think this is due to a new release of testing-farm having issues. It seems like all tests fail somewhere between Jenkins and testing-farm; Jenkins sends a request to testing-farm, and if you find the log of that request - e.g. https://api.dev.testing-farm.io/v0.1/requests/c9516c80-5375-4548-9e52-c8b22… is one - they all have an error like this: "Command '['ssh', 'artifacts.dev.testing-farm.io', 'mkdir', '-p', '/archive/c9516c80-5375-4548-9e52-c8b22f838dac']' failed with exit code 1" I've tried to ping the relevant folks about this, but it may be past the end of their work day. I don't have the knowledge or access to fix this myself unfortunately. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

Zuul not triggering
by Carlos Rodriguez-Fernandez 09 Apr '24

09 Apr '24

Hi, Zuul CI has not been triggering, at least since yesterday. Could someone please look into it? Thank you! Carlos R.F.

4 5

Help Requested: Prevent CI Errors before DNF5 will replace DNF
by Nicola Sella 20 Mar '24

20 Mar '24

Hi all, I am looking for feedback and guidance on how to test DNF5 against Fedora CI. I'd like to start this discussion before the obsolete switch is turned on to avoid any disruption.[1] Currently, the team's plan is to build a side-tag with the DNF-to-DNF5 switch on, and advertise that on the Fedora devel list to gather feedback and allow users/teams to test their builds/workflows in the side-tag. Furthermore, I'd like to put together, or update, a list of requirements to ease the transition from DNF to DNF5. Any recommendations or ideas that should be followed to test DNF5 in Fedora CI? Thanks, Nicola [1]: https://pagure.io/fedora-ci/general/issue/416

2 1

[release] Testing Farm 2024-02.1
by Jan Havlin 07 Mar '24

07 Mar '24

Hi, Testing Farm release 2024-02.1 <https://docs.testing-farm.io/Testing%20Farm/0.1/releases/2024-02.1.html> is deployed 🎉. 💔 Breaking Changes The multihost testing from now uses tmt run provision --update-missing, see docs <https://tmt.readthedocs.io/en/stable/stories/cli.html#update-missing>. This means it will update the image attribute in provision step with the environemnts[].compose API field only if it is not set in the plan. This might break your current multihost plans. Please update your plans accordingly. 🚀 Upgrades Testing Farm CLI <https://docs.testing-farm.io/Testing%20Farm/0.1/cli.html> tool updated from v0.0.16 to v0.0.17 <https://gitlab.com/testing-farm/cli/-/releases/v0.0.17>, please update your installation. 🎯 Highlights Created RFD2 <https://docs.testing-farm.io/Testing%20Farm/0.1/rfd/rfd2-testing-farm-repo-…> for the Testing Farm in config repo which allows configuring secrets in the repository(TFT-1813 <https://issues.redhat.com/browse/TFT-1813>). Feel free to provide feedback to this planned major feature of Testing Farm. Added support by selecting tmt tests by name via the --test option in CLI or test.tmt.test_name field in the API (TFT-2421 <https://issues.redhat.com/browse/TFT-2421>). RHEL-9.5.0 available on Red Hat ranch (TFT-2434 <https://issues.redhat.com/browse/TFT-2434>). CentOS Stream 10 available on Public ranch (TFT-2442 <https://issues.redhat.com/browse/TFT-2442>). Multi-host now uses tmt run provision --update-missing improving the multi-host testing by filling in only missing compose (TFT-2379 <https://issues.redhat.com/browse/TFT-2379>). Testing Farm now prints a warning when how: artemis is used in provision step (TFT-2306 <https://issues.redhat.com/browse/TFT-2306>) and crashes when anything else other than how: container or how is unspecified (TFT-2320 <https://issues.redhat.com/browse/TFT-2320>). Fedora CI docs <https://docs.fedoraproject.org/en-US/ci/testing-farm/> now document Testing Farm as their testing infrastructure (TFT-938 <https://issues.redhat.com/browse/TFT-938>). Added support for configuring how many plans should be executed in parallel via the --parallel-limit option in the CLI or settings.pipeline.parallel-limit field in the API (TFT-2262 <https://issues.redhat.com/browse/TFT-2262>). Automated importing of updates-nightly composes (TFT-2401 <https://issues.redhat.com/browse/TFT-2401>). Added an artifacts link to results viewer page of a running TF test ( TFT-2405 <https://issues.redhat.com/browse/TFT-2405>). Xunit is generated also in case of pipeline errors (TFT-544 <https://issues.redhat.com/browse/TFT-544>). Time attribute is now shown in xunit and results viewer (TFT-2007 <https://issues.redhat.com/browse/TFT-2007>). 🐞 Bugfixes Test environment variable TESTING_FARM_REQUEST_USERNAME is now available again (TFT-2433 <https://issues.redhat.com/browse/TFT-2433>). Leakage of secrets in testout.log was fixed (TFT-2462 <https://issues.redhat.com/browse/TFT-2462>). Fixed a bug where volumes from deployments in EKS clusters were not tagged ( TFT-2313 <https://issues.redhat.com/browse/TFT-2313>). Fixed showing incomplete pipeline.log file in the artifacts (TFT-2451 <https://issues.redhat.com/browse/TFT-2451>). Fixed incorrect Beaker filter for virtualization.is-supported and aarch64 ( TFT-2453 <https://issues.redhat.com/browse/TFT-2453>). Fixed an issue with artifact artifaction at the end of the pipeline ( TFT-2413 <https://issues.redhat.com/browse/TFT-2413>). 🫂 Contributors We would like to thank the following external contributors for contributing to Testing Farm. - Inessa Vasilevskaya — in Testing Farm CLI, arch is passed into tmt context (cli!97 <https://gitlab.com/testing-farm/cli/-/merge_requests/97> ). 📦️ Packages List of important packages bundled in the worker image. ❯ podman run --entrypoint rpm quay.io/testing-farm/worker:2024-02.1 -q tmt standard-test-roles ansible-core podman beakerlib | sort | uniq ansible-core-2.14.11-2.fc38.noarch beakerlib-1.29.3-2.fc38.noarch podman-4.9.3-2.fc38.x86_64 standard-test-roles-4.11-2.fc38.noarch tmt-1.31.0-1.fc38.noarch 🔎 Stats Testing Farm is on track to surpass 1.1M requests per year <https://stats.testing-farm.io/d/dpYooDIVk/testing-farm-all-time-stats> \o/. Error rate in February was approximately 2.88% <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?viewPanel=12&orgId=…> . Around 98k testing requests <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?viewPanel=8&orgId=1…> were recorded in February. Average queue time in February was 1.33 minutes on the Public ranch <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?viewPanel=26&orgId=…> and 3.54 minutes on the Red Hat ranch <http://metrics.osci.redhat.com/d/NnHWU1dnz/testing-farm?viewPanel=27&orgId=…> .

1 0

Re: Update gumbo-parser to 0.12.1/libgumbo SONAME bump
by Adam Williamson 01 Mar '24

01 Mar '24

On Fri, 2024-03-01 at 13:27 -0600, Jason Tibbitts wrote: > > > > > > Adam Williamson <adamwill(a)fedoraproject.org> writes: > > > Honestly, we could really use more automation here, but it's a fairly > > hard thing to do *reliably* and there just isn't anybody specifically > > tasked with it so it doesn't happen. > > So sure, we could use something but it doesn't have to start out as some > complex fully automatic system. (Would be nice, but...) > > Can we agree that we'd be at least half of the way there if we just had > a well defined way to: > > * Know what package depend on the one you're updating > > * Easily bump and chain-build all of that in a side tag > > Surely there's a reopquery or fedrq command line that will find at least > most of what needs to be rebuilt. It doesn't have to be absolutely > perfect but it can't be that hard to get close. I know there's a > distinction between build and runtime dependencies and rich/conditional > dependencies complicate things a bit, but those much smarter than I am > must have already figured out how to get something that's at least > somewhat useful. > > Once you have the package list, maybe it needs some kind of sorting > before you can just bump and chain-build things, but I think in many > cases it doesn't. So, yes, a 100% tool would be really hard but the 80% > tool really shouldn't be that bad, and almost any tool would really help > people out. Yeah, for sure, that's why I'm trying to nibble around the edges by updating the docs to strongly encourage chain builds, document using fedpkg chain-build on a side tag, and hopefully get fedpkg chain-build enhanced so it can create the side tag and the final update automatically. If we can get that, then I can make the docs explain how to use it. ISTR there've been several recent discussions of complex dep chains on this very list where people have floated candidates for repoquery/fedrq commands...if there's one we're pretty confident is The Best, we can definitely plumb that into the docs at least (plumbing it all the way into fedpkg might be a step too far, though). -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2024

2023

2022

2021

2020

2019

2018

2017

CI