We are running canary-package updates to test our infrastructure (mostly bodhi, greenwave, waiverdb, results-db) and this of course touches CI.
This morning I found several updates that seem to be having unexpected problems in CI.
All of these are multi-package updates and all of them had problem with the update test.
We'd like to resolve if it is: * problem with the infrastructure * problem with the update/packages
@asaleh hi, those tests are fairly fresh, looking into details now
CC @msrb
And good somebody is watching :)
Metadata Update from @msrb: - Issue assigned to msrb
I rerun all the jobs, as some of them were caused by an issue I fixed this morning, looking for the next runs
Metadata Update from @mvadkert: - Assignee reset
Metadata Update from @mvadkert: - Issue assigned to msrb
Right, so fedora-ci.koji-build.installability.functional test is still broken, those errors can be safely ignored for now
fedora-ci.koji-build.installability.functional
The test fedora-ci.koji-build.tier0-tf.functional fails as designed:
fedora-ci.koji-build.tier0-tf.functional
https://src.fedoraproject.org/rpms/dummy-test-package-crested/blob/master/f/tests/tests.yml
The tests fedora-ci.koji-build.rpminspect.static-analysis fail as there is no proper disttag ...
fedora-ci.koji-build.rpminspect.static-analysis
https://koji.fedoraproject.org/koji/packageinfo?packageID=30500
@asaleh could these builds be built with dist-tag? so this test can actually work?
@asaleh ping, can we fix the dist-tag sometime? Should we keep this issue open for that?
The original reported issue is gone.
We can workaround the missing release string in CI: rpminspect has --release option that is used in cases like these -- when packages don't have the release string.
--release
So this problem should go away once https://github.com/fedora-ci/rpminspect-pipeline/pull/5 is merged.
The pull request is merged. Let's test it over the weekend and if we don't see these problems anymore, we can close this issue.
@msrb nice, looking at last results for these packages it now works well, disttag test is failed :trident:
Indeed \o/ closing :)
Metadata Update from @msrb: - Issue status updated to: Closed (was: Open)