Fedora 33 pipeline -- is it stuck?

[Jan Pazdziora]

Hello,

I've built package for rawhide

	https://bodhi.fedoraproject.org/updates/FEDORA-2020-f33380047f

and the fedora-ci.koji-build.tier0.functional result

	https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/je...

showed up within 20 minutes.

I then built the same package for Fedora 33

	https://bodhi.fedoraproject.org/updates/FEDORA-2020-1b4c8966de

and the WebUI says

	 1 of 1 required test results missing

and looking at the Jenkins pipeline

	https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/je...

no jobs for swid-tools is even there, the last one completed a day ago.

Is that expected?

-- 
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat

[Bruno Goncalves]

On Fri, Sep 25, 2020 at 2:22 PM Jan Pazdziora <jpazdziora(a)redhat.com&gt; wrote:
>  Hello,
>
>  I've built package for rawhide
>
>          https://bodhi.fedoraproject.org/updates/FEDORA-2020-f33380047f
>
>  and the fedora-ci.koji-build.tier0.functional result
>
>         
> https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/je...
>
>  showed up within 20 minutes.
>
>  I then built the same package for Fedora 33
>
>          https://bodhi.fedoraproject.org/updates/FEDORA-2020-1b4c8966de
>
>  and the WebUI says
>
>           1 of 1 required test results missing
>
>  and looking at the Jenkins pipeline
>
>         
> https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/je...
>
>  no jobs for swid-tools is even there, the last one completed a day ago.
>
>  Is that expected? 
For
https://bodhi.fedoraproject.org/updates/FEDORA-2020-1b4c8966de it
is expected.
The test will be triggered once bodhi promotes it to testing status.
Currently it is on "pending->testing"

Bruno
>  --
>  Jan Pazdziora
>  Product Owner, Platform Security Readiness, Red Hat
>  _______________________________________________
>  CI mailing list -- ci(a)lists.fedoraproject.org
>  To unsubscribe send an email to ci-leave(a)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/[e-mail]

[Jan Pazdziora]

On Fri, Sep 25, 2020 at 02:44:01PM +0200, Bruno Goncalves wrote:
>  For https://bodhi.fedoraproject.org/updates/FEDORA-2020-1b4c8966de
> it
>  is expected.
>  The test will be triggered once bodhi promotes it to testing status.
>  Currently it is on "pending->testing" 
Does the testing status correspond to the build being added to the
testing repository? Why does CI need to wait for that, rather than
run the tests right away?

-- 
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat

[Bruno Goncalves]

On Fri, Sep 25, 2020 at 3:10 PM Jan Pazdziora <jpazdziora(a)redhat.com&gt; wrote:
>  On Fri, Sep 25, 2020 at 02:44:01PM +0200, Bruno Goncalves wrote:
>  > For https://bodhi.fedoraproject.org/updates/FEDORA-2020-1b4c8966de it
>  > is expected.
>  > The test will be triggered once bodhi promotes it to testing status.
>  > Currently it is on "pending->testing"
>
>  Does the testing status correspond to the build being added to the
>  testing repository? Why does CI need to wait for that, rather than
>  run the tests right away? 
This was implemented as part of https://pagure.io/fedora-ci/general/issue/70.
If there is need to trigger on other event we can discuss it, but
please open an issue on https://pagure.io/fedora-ci/general/new_issue

More details about bodhi states can be found on
https://fedoraproject.org/wiki/Bodhi#Package_States

Bruno

>  --
>  Jan Pazdziora
>  Product Owner, Platform Security Readiness, Red Hat
>  _______________________________________________
>  CI mailing list -- ci(a)lists.fedoraproject.org
>  To unsubscribe send an email to ci-leave(a)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/[e-mail]

[Jan Pazdziora]

On Fri, Sep 25, 2020 at 04:38:35PM +0200, Bruno Goncalves wrote:
>  
>  This was implemented as part of https://pagure.io/fedora-ci/general/issue/70.
>  If there is need to trigger on other event we can discuss it, but
>  please open an issue on https://pagure.io/fedora-ci/general/new_issue 
Thanks for the pointer, I've filed

	https://pagure.io/fedora-ci/general/issue/146

now.

-- 
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat

[Jan Pazdziora]

On Fri, Sep 25, 2020 at 02:44:01PM +0200, Bruno Goncalves wrote:
>  For https://bodhi.fedoraproject.org/updates/FEDORA-2020-1b4c8966de it
>  is expected.
>  The test will be triggered once bodhi promotes it to testing status.
>  Currently it is on "pending->testing" 
Hello, I have another Fedora 33 update

	https://bodhi.fedoraproject.org/updates/FEDORA-2020-b727e91aa8

and it has been in the testing status for two weeks but the test did
not seem to materialize. Is that expected?

-- 
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat

[Bruno Goncalves]

On Thu, Oct 22, 2020 at 9:32 AM Jan Pazdziora <jpazdziora(a)redhat.com&gt; wrote:
>  On Fri, Sep 25, 2020 at 02:44:01PM +0200, Bruno Goncalves wrote:
>  >
>  > For https://bodhi.fedoraproject.org/updates/FEDORA-2020-1b4c8966de it
>  > is expected.
>  > The test will be triggered once bodhi promotes it to testing status.
>  > Currently it is on "pending->testing"
>
>  Hello, I have another Fedora 33 update
>
>          https://bodhi.fedoraproject.org/updates/FEDORA-2020-b727e91aa8
>
>  and it has been in the testing status for two weeks but the test did
>  not seem to materialize. Is that expected? 
It is not expected, the test should trigger once the update lands on
"testing" state.
In this case for some reason the pipeline missed the trigger message.
We are in the process of moving the pipeline to a new cluster that
should help in cases like this.

Anyway, I've triggered it manually now:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f33-build-...

Btw, you should be able to retrigger the test by running "bodhi
updates trigger-tests <update id>"

Bruno

>  --
>  Jan Pazdziora
>  Product Owner, Platform Security Readiness, Red Hat
>  _______________________________________________
>  CI mailing list -- ci(a)lists.fedoraproject.org
>  To unsubscribe send an email to ci-leave(a)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/[e-mail]

[Jan Pazdziora]

On Thu, Oct 22, 2020 at 09:42:30AM +0200, Bruno Goncalves wrote:
>  
>  It is not expected, the test should trigger once the update lands on
>  "testing" state.
>  In this case for some reason the pipeline missed the trigger message.
>  We are in the process of moving the pipeline to a new cluster that
>  should help in cases like this.
>  
>  Anyway, I've triggered it manually now:
>
> https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f33-build-...
Thanks.

>  Btw, you should be able to retrigger the test by running "bodhi
>  updates trigger-tests <update id>" 
Any chance of making this available in the Bodhi WebUI? For these
tasks that are only rarely needed, reminding people visually what the
possible actions are might be useful.

-- 
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat

[Bruno Goncalves]

On Thu, Oct 22, 2020 at 9:55 AM Jan Pazdziora <jpazdziora(a)redhat.com&gt; wrote:
>  On Thu, Oct 22, 2020 at 09:42:30AM +0200, Bruno Goncalves wrote:
>  >
>  > It is not expected, the test should trigger once the update lands on
>  > "testing" state.
>  > In this case for some reason the pipeline missed the trigger message.
>  > We are in the process of moving the pipeline to a new cluster that
>  > should help in cases like this.
>  >
>  > Anyway, I've triggered it manually now:
>  >
> https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f33-build-...
>
>  Thanks.
>
>  > Btw, you should be able to retrigger the test by running "bodhi
>  > updates trigger-tests <update id>"
>
>  Any chance of making this available in the Bodhi WebUI? For these
>  tasks that are only rarely needed, reminding people visually what the
>  possible actions are might be useful. 
For that I think you need to open an RFE for Bodhi, I'm not sure what
is the best place for it, maybe on
https://github.com/fedora-infra/bodhi/issues ...

>  --
>  Jan Pazdziora
>  Product Owner, Platform Security Readiness, Red Hat
>  _______________________________________________
>  CI mailing list -- ci(a)lists.fedoraproject.org
>  To unsubscribe send an email to ci-leave(a)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/[e-mail]

[Jan Pazdziora]

On Thu, Oct 22, 2020 at 10:07:35AM +0200, Bruno Goncalves wrote:
>  On Thu, Oct 22, 2020 at 9:55 AM Jan Pazdziora
> <jpazdziora(a)redhat.com&gt; wrote:
>  > On Thu, Oct 22, 2020 at 09:42:30AM +0200, Bruno Goncalves wrote:
>  > >
>  > > Btw, you should be able to retrigger the test by running "bodhi
>  > > updates trigger-tests <update id>"
>  >
>  > Any chance of making this available in the Bodhi WebUI? For these
>  > tasks that are only rarely needed, reminding people visually what the
>  > possible actions are might be useful.
>  
>  For that I think you need to open an RFE for Bodhi, I'm not sure what
>  is the best place for it, maybe on
>  https://github.com/fedora-infra/bodhi/issues ... 
Great, thanks -- I've filed

	https://github.com/fedora-infra/bodhi/issues/4144

now.

-- 
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat