pre-commit fails to install on rawhide. It is listed in health check and also has a F33FailsToInstall bugzilla. Yet it is not listed as FTI in the dashboard.
Metadata Update from @lbrabec: - Issue assigned to lbrabec
Metadata Update from @frantisekz: - Assignee reset
Metadata Update from @frantisekz: - Issue assigned to frantisekz
So, for FTI bug, there is one openned which is both FTBFS and FTI, I guess that's the problem for current implementation ( https://bugzilla.redhat.com/show_bug.cgi?id=1836333 ).
Looking at health-check report, I am looking at "affected key" in https://pagure.io/fedora-health-check/raw/master/f/data/report-rawhide.json and pre-commit is listed there only under user "atim".
I'll improve both paths of health-check parsing code to take these cases into account.
So, for bugs codepath, api returns FTI keyword just fine for churchyard, but frontend doesn't dipslay FTI tag:
"pre-commit": [ { "bug_id": 1836333, "comments": 3, "keywords": [ "FTBFS", "FTI" ], "modified": "20200601T10:32:56", "release": "rawhide", "reported": "20200515T16:08:18", "severity": "unspecified", "status": "NEW", "title": "pre-commit fails to build with Python 3.9: 3 test failures related to python.healthy", "url": "https://bugzilla.redhat.com/1836333" } ],
From Miro's comment I assumed that it is better to ignore keywords in bugzilla and use only koschei for FTBFS and fedora health check for FTI.
Fixed by https://pagure.io/fedora-qa/oraculum/c/cf9175870abad970ccdb57df3670b5cf4971f4d0?branch=master
Fix deployed on server, data manually refreshed for @churchyard (others will be refreshed in up to 2 hours).
Metadata Update from @frantisekz: - Issue status updated to: Closed (was: Open)
Thanks. I think that healhcheck only returns main admins, but I will, check.
correct, healhcheck only returns main admins
https://pagure.io/fedora-health-check/blob/master/f/internals.py#_214
I also see "cura" as not reported. That one is even mine (I am the main admin).
Metadata Update from @churchyard: - Issue status updated to: Open (was: Closed)
I see FTI for "cura" both on our test instance and back-end response. Could it be that data weren't synced yet?
My bad. https://pagure.io/fedora-qa/packager_dashboard/c/e4d257e2dbe8aeaa181d8ec62c18f5bf534e3ec0?branch=master caused all my FTI reports to be hidden.
Metadata Update from @churchyard: - Issue status updated to: Closed (was: Open)
Oh, my bad! I think it was caused by "old" settings object in local storage, key show_fti was missing and was resolved to undefined which in JS is interpreted as false if used as boolean.
show_fti
undefined
false
I try to remember to tell to delete local storage for breaking changes next time.
Log in to comment on this ticket.