Thanks to @decathorpe for catching these issues. The first instance was with this update, where the test links in the update point to a 404 page: - fedora-ci.koji-build.tier0.functional - fedora-ci.koji-build.installability.functional - fedora-ci.koji-build.rpminspect.static-analysis
I have tried to retrigger the tests manually via the jenkins dashboard, but I got hit by a different issue.
But now I've found it to have occurred in another place at a different timepoint: https://src.fedoraproject.org/rpms/fprintd/pull-request/5 - Fedora CI - dist-git test
Anyone have ideas on how to track down the source of these?
Yes, this is most probably caused because the Jenkins is setup to keep only last 3 days of logs, what is not much. @lecris I am thinking about raising this to at least 7 days, an the most ideal solution would be to keep for longer only the failures. Let's get back to this later this week.
When I checked the PR one I believe it was only 2 days old, but maybe I misremember. Anyway let's see what we can do to raise the retention of these.
Metadata Update from @lecris: - Issue status updated to: Closed (was: Open)