No worries, you're getting work done and email filters are easy enough to create!
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Benjamin Mahler <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, June 27, 2013 10:51 AM To: "[email protected]" <[email protected]> Subject: Jenkins Noise >Hey all, sorry for the noise overnight on Jenkins. > >It seems we're getting an excess of email due to >JENKINS-18079<https://issues.jenkins-ci.org/browse/JENKINS-18079>. >It looks like many of the slaves go offline when idle, which appears to >cause a loss of the previous revision information. The polling logs >indicate there's a non-existing workspace, which is why it is building >multiple times on the same git revision: > >Started on Jun 27, 2013 4:40:09 PM >Workspace is offline. >Scheduling a new build to get a workspace. (nonexisting_workspace) >Done. Took 0 ms >Changes found > > >For now, I'm going to leave on the setting that sends an email for each >unstable build as it allows us to catch flaky tests. I've also changed the >tests to run for 5 iterations to help further catch any remaining flaky >tests. > >Will be quicker to fix in the future, again sorry for the noise! > >Ben
