On Fri, Apr 28, 2017 at 5:28 PM, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > Apparently something happened to out Jenkins system during an upgrade > so it was out for a while. One of the CC'ed guys can hopefully provide > some details. > -Greg > > On Thu, Apr 27, 2017 at 8:05 AM Willem Jan Withagen <wjw@xxxxxxxxxxx> wrote: >> >> On 27-4-2017 16:52, Willem Jan Withagen wrote: >> > Hi, >> > >> > Is there any particulars why I have 4 PRs that are held on trial runs >> > thru Jenkins? Hey Willem, apologies for taking so long to respond, Greg Meno just sent an update to the sepia mailing list, but let me give a tl;dr here as well: * We upgraded our Jenkins master instance to address a security issue on the same day it was released * After the upgrade all of the slaves lost connectivity because the security upgrade brought in some incompatibilities on how we connect * Several hours after debugging and submitting upstream patches on the libraries we depend on we were able to get back almost back to normal Even after being able to connect some other jobs and slaves continued to have some issues that took an extra day to resolve (mostly ceph-ansible which relies on libvirt hosts). I had initially sent out an email to a non-public facing email list and I should've followed up with ceph-devel too. Thanks Gregory for pinging us and letting us know that we missed out on that Apologies again for the delay >> >> 'mmm, >> >> Some/All of them "just" started to be processed. >> So I guess the queue was rather full. >> >> --WjW >> >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
