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. Thanks, Alex -----Original Message----- From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Mats Wichmann Sent: Tuesday, September 26, 2017 12:48 PM To: iotivity-dev@lists.iotivity.org Subject: Re: [dev] Status of Jenkins On 09/26/2017 01:34 PM, Alex Kelley via iotivity-dev wrote: > Hi, > > Did Jenkins just restart? About an hour ago I was checking the status of a > build and saw a red banner indicating that Jenkins was shutting down but it > has disappeared now. If so, could we get some more communication on when > these restarts will happen? I've been trying to get some changes to build for > a couple of days but keep hitting issues. Yesterday Jenkins was unavailable > (I assume this was unscheduled) and today I didn't want to retrigger the > specific build because I wasn't sure if Jenkins was going down and for how > long. it had an emergency restart a few hours ago because no build sets were completing (what you were seeing, but it got even worse) LF staff applied a fix which hopefully will help. At some point in the past, a switch was made from completely instantiating images fresh each time to leaving them set up - I'm presuming that was to (a) decrease startup time and (b) reduce load during startup. Anyway, the side effect was that some state was lying around and it has led to lots of disk-full problems. Today's change was to commit a pending change to do cleanup in between runs. This is my understanding - it's not the "official word" but I'm trying the best I can to keep on top of it, and harass people (slight grin). It has indeed been really frustrating that for some time now, it's hard to reliably count on a given build set going through without tripping over something that wasn't related to the change being made. _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7Calexke%40microsoft.com%7C95c35a15f8da410c1b0e08d505177fea%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636420520875942102&sdata=P9I8UuWpKNOo1%2FsN0OJwhUEfjnP0YH7zh8u6z8zEAQw%3D&reserved=0 _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
