On Thu, Jun 13, 2019 at 3:10 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno gio 13 giu 2019 alle ore 11:15 Sandro Bonazzola <sbonazzo@redhat.com> ha scritto:Il giorno gio 13 giu 2019 alle ore 08:34 Edward Haas <edwardh@redhat.com> ha scritto:On Mon, Jun 10, 2019 at 11:00 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:Il giorno mer 5 giu 2019 alle ore 09:52 Sandro Bonazzola <sbonazzo@redhat.com> ha scritto:Il giorno mer 5 giu 2019 alle ore 09:08 Nir Soffer <nsoffer@redhat.com> ha scritto:On Wed, Jun 5, 2019, 08:32 Sandro Bonazzola <sbonazzo@redhat.com> wrote:Hi,while we are introducing support for fedora 29 and 30 we need to free resources both on jenkins and on resources.ovirt.org.Starting today I'll start pushing removal of fc28 jenkins jobs. Once done, I'm going to remove the fc28 repositories from all snapshot and tested repos, keeping fc28 repos only within the released repositories.This is fine once we have working f29 build.Not sure we can wait that much dropping fc28.Right now it takes up to 3 days for a patch to land on snapshot repos due to the amount of time spent by deploy_to_master_tested generating the repositories metadata.And we have space limitations to the amount of builds we can keep on our systems.Fedora 28 jobs are being removed by jenkins right now.If your project is not building on Fedora 29 yet (python 2 only, no need to fix python 3 on fc29 now), please fix it as soon as possible.VDSM jobs require the slaves to be in sync with the mock env (stdci `host-distro: same`), but the tests fail on fc29 (https://gerrit.ovirt.org/#/c/100429/).The last time we saw such failures, we performed this pinning of the version (https://gerrit.ovirt.org/#/c/96921/).Therefore, I would like to check if the slaves OS is updated compared to the mock env.Yes, we have fc29 slaves: https://jenkins.ovirt.org/label/fc29/Evgeny can you give a mass dnf upgrade on the fc29 slaves to ensure they're all updated?
I think this patch should force fc29 slaves to use latest pkgs from the mirrors:
_____________________________________________________________________________________________________________________________________________Thanks,--
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/36OHDZDMIMKCEAG3NXZWOGQGYEV2ARR2/
----
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/HCPFUWMRZRR4VZGLY6HP5P4QDBDD3MDC/
----
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/V7BHZ7SYDWCNUNRTQZPV5O7TI5VJASCR/
