As you may have noticed, this has been a particularly bad week for build stability. This was exacerbated by two outright failures today. The failures occurred, and always occur, when the build runs on ubuntu2 due to a (Too many open files) error. These failures never occur on any other ubuntu machine. I have sent two notes to the [email protected] list asking if the ulimit on ubuntu2 can be checked and, if necessary, matched with the value on the other machines. Until that occurs, I'm proposing that we update the label expression in our build configuration to prohibit running on ubuntu2 in order to avoid this unnecessary churn in the build process. There are 4 other ubuntu machines, so I don't think that will have a noticeable impact at the current level of activity. Would anyone object?
John Apache Jenkins Server <[email protected]> wrote on 11/21/2012 12:13:42 PM: > Apache Jenkins Server <[email protected]> > 11/21/2012 12:13 PM > > Please respond to > [email protected] > > To > > [email protected], John W Ross/Atlanta/IBM@IBMUS, [email protected], > > cc > > Subject > > Jenkins build is back to normal : Aries #1752 > > See <https://builds.apache.org/job/Aries/1752/> >
