updates.html: include satisfied requirements in the table #5388
Conversation
|
Note, this stuff is technically incorrect in another way: for greenwave requirements it does not consider the scenario, which it technically ought to. But in practice, I don't think we have any cases where a given testcase name is required in some scenarios but not others, so for now this will give the correct result. I don't want to fix it any harder for now because if we start making non-trivial changes to this stuff, we should think about #3938 first. It would be nice for this Note, it was probably me who broke this in the first place in one of my previous rearrangements of all this code, so sorry. :) |
I noticed today that tests which are 'required' aren't marked as such in the Bodhi webUI if they passed. Only queued or failed or missing tests are shown as 'required' (as shown by the black asterisk with a mouseover comment, on the Automated Tests tab). This is because we're not pushing satifised requirements into the list that's used to track which tests are required. Signed-off-by: Adam Williamson <awilliam@redhat.com> end
AdamWill
force-pushed
the
mark-satisfied-requirements
branch
from
c817bfb to
725e1f9
Compare
|
Rawhide integration test failure is a CI issue - |
|
I've cherry-picked the change in bodhi.stg and, even if the db is still not updated, I think it's working as expected: |
It's https://pagure.io/fedora-infra/ansible/raw/main/f/files/common/fedora-infra-tags.repo for some reason |
I noticed today that tests which are 'required' aren't marked as such in the Bodhi webUI if they passed. Only queued or failed or missing tests are shown as 'required' (as shown by the black asterisk with a mouseover comment, on the Automated Tests tab). This is because we're not pushing satifised requirements into the list that's used to track which tests are required.