On 09/26/2017 02:26 PM, Alex Kelley wrote: > Thanks for the info Mats! > > Do you know if all of the machines are supposed to have the update at this > time? After the banner disappeared I retriggered a build that had a failure. > It just failed again and it appears to be due to the same issue of the > machine being out of room. Here is a link to the console output: > > https://build.iotivity.org/ci/job/iotivity-verify-tizen_unsecured/3089/console > > A couple of other times where Jenkins needed to be restarted I saw emails go > out to the dev alias indicating that it was going to happen. Is it part of > our policy to send out emails for when Jenkins is down or needs to go down? > If not I think it is something we should consider adding just so everyone has > an idea of what is happening.
if they were scheduled, yes there's been announcements. this time stuff got killed that was going to fail anyway. I think I caused this one by yelling too loudly :) The best way to get a reaction to a builder problem is by filing a ticket - which happens by sending email to: IoTivity Helpdesk via RT <iotivity-helpd...@rt.linuxfoundation.org> however, that doesn't necessarily have wider visibility to the iotivity developers. I think there's some kind of status location one can check, I'll try to dig that out and share if I find it. _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
