Comments
vkadlcik
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
No regression observed
failed test in CI:
baseos-qe.koji-build.scratch-build.validation - broken infrastructure, ran manually, PASS
fedora-ci.koji-build.rpminspect.static-analysis - broken infrastructure, ran manually, only false positives found
fedora-ci.koji-build.rpmdeplint.functional - broken infrastructure, no need to run this now IMHO
In summary, all the failures can be waived
"fedora-ci.koji-build.rpminspect.static-analysis" didn't run at all (infrastructure error). I ran it manually, it reported just known issues: false positives and troubles with clang-based code (RHEL-35947). Can be waived.
"baseos-qe.koji-build.scratch-build.validation" failed in CI. I just re-ran manually it and it passed so it can be waived.
"fedora-ci.koji-build.rpminspect.static-analysis" didn't run at all (infrastructure error). I ran it manually, it reported just known issues: false positives and troubles with clang-based code (RHEL-35947). Can be waived.
"baseos-qe.koji-build.scratch-build.validation" failed in CI. I just re-ran manually it and it passed so it can be waived.
The "fedora-ci.koji-build.tier0.functional" failure in CI can be waived. It's not occur in a fully updated system, just in the somewhat outdated VMs in CI.
I'll look into the "baseos-qe.koji-build.scratch-build.validation" failure tomorrow.
CI failures can be waived:
-
baseos-qe.koji-build.scratch-build.validation: setup error, i re-ran that manually instead, passed
-
fedora-ci.koji-build.rpminspect.static-analysis: /annocheck - known issue: RHEL-35947, /unicode - false positive (CVE-2021-42574 mitigation)
CI: just a false positive in fedora-ci.koji-build.rpminspect.static-analysis
CI failed in fedora-ci.koji-build.rpminspect.static-analysis:
-
the "unicode" failure is a routine false positive
-
/usr/lib/clang/plugins/annobin-for-{llvm,clang}.so fail in annocheck - no problem in practice, those 32-bit libraries don't ship
The required fedora-ci.koji-build.tier0.functional testing failed in CI but it was because of some infrastructure problem. I re-run it in a virtual machine and it passed.
"baseos-qe.koji-build.scratch-build.validation" failed when building kernel on s390x. The cause was an infrastructure error (https://kojipkgs.fedoraproject.org//work/tasks/2249/115072249/checkout.log). I rerun the build successfully: https://koji.fedoraproject.org/koji/taskinfo?taskID=115107590.
Completed my side run of baseos-qe.koji-build.scratch-build.validation. Consider CI as passed.
CI results:
baseos-qe.koji-build.scratch-build.validation - some infrastructure problems, I'm running the test aside, still in progress
fedora-ci.koji-build.rpminspect.static-analysis - false positive
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/