[ovirt-devel] Re: vdsm_standard-check-patch is stuck on Archiving artifacts

Hi, I'm working on this now, I'll update when fixed. On Mon, Aug 19, 2019 at 10:59 AM Amit Bawer <abawer(a)redhat.com&gt; wrote: > Quick/temp solution is also welcomed at this point as i need to verify > patches. Thanks > > On Mon, Aug 19, 2019 at 8:56 AM Amit Bawer <abawer(a)redhat.com&gt; wrote: > >> Seems to happen again: >> https://jenkins.ovirt.org/job/standard-manual-runner/646/console >> >> On Sun, Aug 18, 2019 at 11:31 AM Amit Bawer <abawer(a)redhat.com&gt; wrote: >> >>> Great, thanks for the update. >>> >>> On Sun, Aug 18, 2019 at 10:47 AM Ehud Yonasi <eyonasi(a)redhat.com&gt; >>> wrote: >>> >>>> Hey, >>>> The problem was with mock cache filling up the filesystem and it is >>>> now cleaned. The s390x slave is back online. >>>> >>>> On Sun, Aug 18, 2019 at 10:05 AM Daniel Belenky <dbelenky(a)redhat.com&gt; >>>> wrote: >>>> >>>>> Hi Nir, >>>>> >>>>> It seems that the reason behind this issue is that the s390x node is >>>>> offline. >>>>> I'm checking it right now and will update asap. >>>>> >>>>> On Sat, Aug 17, 2019 at 3:18 AM Nir Soffer <nsoffer(a)redhat.com&gt; >>>>> wrote: >>>>> >>>>>> On Sat, Aug 17, 2019 at 3:06 AM Nir Soffer <nsoffer(a)redhat.com&gt; >>>>>> wrote: >>>>>> >>>>>>> This looks like a bug, so adding infra-support - this will open a >>>>>>> ticket and someone will look into it. >>>>>>> >>>>>>> On Sat, Aug 17, 2019 at 1:12 AM Amit Bawer <abawer(a)redhat.com&gt; >>>>>>> wrote: >>>>>>> >>>>>>>> Hi >>>>>>>> Unable to run CI builds and OSTs due to indefinite processing over >>>>>>>> fc29 Archiving artifacts phase >>>>>>>> Example run: >>>>>>>> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/10453/console >>>>>>>> >>>>>>> >>>>>> We have 2 stuck builds: >>>>>> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/10454/ >>>>>> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/10453/ >>>>>> >>>>>> Both started 4 hours ago. >>>>>> >>>>>> It possible to abort jobs from jenkins UI, but usually it cause more >>>>>> trouble because >>>>>> of partial cleanup, so lets let infra team handle this properly. >>>>>> >>>>>> >>>>>>> _______________________________________________ >>>>>>>> Devel mailing list -- devel(a)ovirt.org >>>>>>>> To unsubscribe send an email to devel-leave(a)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/JU3IZE2IQLV... >>>>>>>> >>>>>>> _______________________________________________ >>>>>> Devel mailing list -- devel(a)ovirt.org >>>>>> To unsubscribe send an email to devel-leave(a)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/3LAOTG5RQDY... >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Daniel Belenky >>>>> >>>>> Red Hat <https://www.redhat.com/> >>>>> <https://red.ht/sig> >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list -- devel(a)ovirt.org >>>>> To unsubscribe send an email to devel-leave(a)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/5A34H2SKDT2... >>>>> >>>> _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)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/HMLTPDVJKAS... > -- Emil Natan RHV/CNV DevOps