OK, baseos-qe.koji-build.scratch-build.validation passed. To sum it up, all the gating tests either passed in CI or I can waive them.
fedora-ci.koji-build.installability.functional done, not funny. Misled by https://github.com/fedora-ci/mini-tps. The actual procedure was: get an updated Fedora Rawhide machine and there:
dnf copr enable @osci/mini-tps
dnf -y install mini-tps
mtps-prepare-system --list
PROFILE_NAME=fedora-42
export TASK_ID=125886205
git clone https://github.com/fedora-ci/installability-pipeline.git
cd installability-pipeline
cat installability.fmf
bash prepare.sh
/usr/local/libexec/mini-tps/installability_runner.sh --critical --skiplangpack --selinux=1 --repo=brew-$TASK_ID
echo $?
At this moment, the only remaining test job is baseos-qe.koji-build.scratch-build.validation...
Great. Even the tests that passed on the first attempt are now failing because of infrastructure problems. Once again manual effort necessary, sigh...
fedora-ci.koji-build.tier0.functional is fine, passed originally and in my manual run as well
fedora-ci.koji-build.rpminspect.static-analysis has just one minor annocheck thing, already solved, popping up here only because rpminspect is still using older annobin-libannocheck
baseos-qe.koji-build.scratch-build.validation is in progress
fedora-ci.koji-build.installability.functional - will do manually
[citest]
[citest]
CI findings:
fedora-ci.koji-build.rpminspect.static-analysis - not a regression, low prio https://bugzilla.redhat.com/show_bug.cgi?id=2323797
baseos-qe.koji-build.scratch-build.validation - just a glitch, not a problem of annobin
No regression seen, feel free to promote the build.
All right, baseos-qe.koji-build.scratch-build.validation passed.
In summary, the gating failures are not important. Feel free to promote the build.
Gating failures:
fedora-ci.koji-build.rpminspect.static-analysis - Not a regression. Nevertheless I've just filed it as https://bugzilla.redhat.com/show_bug.cgi?id=2323797. It would be nice not to inspect the failing test on each and every build...
baseos-qe.koji-build.scratch-build.validation - I'm rerunning it aside right now. Will need a few hours, then I'll report back.
The mandatory test "baseos-qe.koji-build.scratch-build.validation" failed but it looks like an infrastructure issue. All the builds were properly started and ended up successfully:
https://koji.fedoraproject.org/koji/taskinfo?taskID=125281620 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281621 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281623 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281627 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281628 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281629 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281630 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281631 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281632 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281633 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281634 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281640 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281641 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281642 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281643 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281659 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281664 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281666 https://koji.fedoraproject.org/koji/taskinfo?taskID=125281925
@jakub, feel free to ignore the failure.
FWIW, I've just sent a PR to rpminspect so the unicode false positives won't bother us in the future: https://github.com/rpminspect/rpminspect-data-fedora/pull/59
There are two gating tests failing:
baseos-qe.koji-build.scratch-build.validation - strace can't be rebuilt but it's a known strace bug unrelated to annobin (https://bugzilla.redhat.com/show_bug.cgi?id=2317070)
fedora-ci.koji-build.rpminspect.static-analysis - same old, same old
Nick, feel free to promote the build.
fedora-ci.koji-build.tier0.functional failed because it uses an older version of the downstream tests (incompatible with the new rpmbuild layout), it would pass with the new version already present in Rawhide.
Feel free to waive that and promote the build
I've prepared a PR to update the tests in F41: https://src.fedoraproject.org/rpms/dwz/pull-request/16. The dist-git test (ie. fedora-ci.koji-build.tier0.functional) passed there.
Failures seen in Automated Tests:
update.desktop_printing failed because of some cgroups stuff, unrelated to dwz. It's not a required test anyway, can be ignored.
fedora-ci.koji-build.tier0.functional failed because it had used the old version of the tests (ie. before https://src.fedoraproject.org/rpms/dwz/pull-request/15). Looks like one needs to do a rebuild for CI to pick up on the merge. The new version passes:
git clone https://src.fedoraproject.org/rpms/dwz.git
cd dwz
testing-farm request --arch=x86_64 --hardware=memory=">= 8 GiB" --hardware=disk.size=">= 60 GiB" --compose=Fedora-Rawhide-Nightly --fedora-koji-build=dwz-0.15-8.fc42 -c distro=fedora-rawhide -c arch=x86_64 --plan=/plans/ci
See the result at https://artifacts.osci.redhat.com/testing-farm/f0cbfed4-1540-468f-b1cb-943724b9c581/
Overall, feel free to waive the tests and promote the build.
Just for the record, the failure of fedora-ci.koji-build.tier0.functional was not caused by any genuine bug in the update, it was the test that needed a change to keep up with the updated package. Fixed now: https://artifacts.osci.redhat.com/testing-farm/3e49d419-c11e-465c-8d94-1488472df9eb/
CI failed in two tests:
baseos-qe.koji-build.scratch-build.validation - that was just an infrastructure error, all the rebuilds worked fine
fedora-ci.koji-build.rpminspect.static-analysis - missing results due to some infrastructure error. I ran it manually and filed https://bugzilla.redhat.com/show_bug.cgi?id=2295573. Not a blocker, though.
BZ#2294381 has been fixed. I'd suggest to push the build to production.
Forgot to mention, CI reported one fail in fedora-ci.koji-build.tier0.functional but that was a problem in the test itself (which I've just fixed).
No regression observed
No regression observed
@msrb Yup, found and used it later...