Re: container-selinux F32 updates never go to stable

2020-08-05 Thread Andre Robatino
The update was obsoleted, but it looks like your fix worked on its replacement. 
The new update https://bodhi.fedoraproject.org/updates/FEDORA-2020-04374575bf 
now shows "All required tests passed". Thanks!
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Re: container-selinux F32 updates never go to stable

2020-08-05 Thread Adam Williamson
On Wed, 2020-08-05 at 08:34 +, Andre Robatino wrote:
> For about the last 2 months, no F32 container-selinux update has been
> able to go to stable. This is due to a single failed test which for
> some reason, only applies to F32 but not F31. The latest update is 
> https://bodhi.fedoraproject.org/updates/FEDORA-2020-30e48495bf which
> is now submitted for stable but will never get there. Putting these
> updates in bodhi, having them get upvotes, then be obsoleted over and
> over because they are ejected from the push due to the failed test
> seems like the definition of insanity. I've asked in bodhi comments
> what is going on but no one responds. There's nothing in bugzilla,
> but I wouldn't expect it, this seems to be a QA issue (the failed
> test that only applies to F32).

It's actually a packaging issue. The package repo itself defines what
tests are gating:

https://src.fedoraproject.org/rpms/container-selinux/blob/f32/f/gating.yaml

the problem is that the name given there is no longer correct. Fedora
CI has been changed since it was set up. The name was updated on the
master branch:

https://src.fedoraproject.org/rpms/container-selinux/c/92fc7eb0900a18b297818a6ef00083011c11a513?branch=master

but not on the f32 branch. Fortunately, as I'm a provenpackager, I can
fix that :) CCing Aleksandra for info. I'm not sure what needs to be
done for the gating.yaml change to be taken into account after I make
it - not sure if the update needs to be edited, or a new build needs to
be done, or if nothing needs doing and Bodhi will re-check the decision
of its own accord.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


container-selinux F32 updates never go to stable

2020-08-05 Thread Andre Robatino
For about the last 2 months, no F32 container-selinux update has been able to 
go to stable. This is due to a single failed test which for some reason, only 
applies to F32 but not F31. The latest update is 
https://bodhi.fedoraproject.org/updates/FEDORA-2020-30e48495bf which is now 
submitted for stable but will never get there. Putting these updates in bodhi, 
having them get upvotes, then be obsoleted over and over because they are 
ejected from the push due to the failed test seems like the definition of 
insanity. I've asked in bodhi comments what is going on but no one responds. 
There's nothing in bugzilla, but I wouldn't expect it, this seems to be a QA 
issue (the failed test that only applies to F32).
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org