On 16 Nov 2021, at 20:42, Milan Zamazal <mzamazal@redhat.com> wrote:
Hi,
putting recently experienced problems with OST runs failures aside, I wonder about what currently happens in gerrit on gating. For instance in https://gerrit.ovirt.org/c/vdsm/+/117523/6:
- OST OST -1 Patch Set 6: OST-1 https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4579 : Looking for build artifacts for OST. ci build
* Why setting OST-1 when looking for a build?
- Jenkins CI Patch Set 6:
No Builds Executed
https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30672/ : To avoid overloading the infrastructure, a whitelist for running gerrit triggered jobs has been set in place, if you feel like you should be in it, please contact infra at ovirt dot org.
* OST not allowed to trigger builds?
- OST OST +1 Patch Set 6: OST+1
https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4583 : start OST for https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30681/
* Shouldn't OST set OST+1 after it runs rather than when it starts?
Yes. I looked at it today and hopefully fixed. There is no history for server configuration in jenkins. Either someone changed that or it happened on some upgrade. No idea, best would be to report it when you notice, not a week later
Is there any explanation of these phenomenons?
Thanks, Milan _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IMRYKBROJXKU3E...