[Buildbot-commits] buildbot ChangeLog,1.329,1.330 NEWS,1.33,1.34

[Brian Warner]

Update of /cvsroot/buildbot/buildbot
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11588

Modified Files:
	ChangeLog NEWS 
Log Message:
Revision: arch at buildbot.sf.net--2004/buildbot--dev--0--patch-10
Creator:  Brian Warner <warner at lothar.com>

NEWS: update for stuff since last release

2004-12-05  Brian Warner  <warner at lothar.com>

   * NEWS: update for stuff since last release


Index: ChangeLog
===================================================================
RCS file: /cvsroot/buildbot/buildbot/ChangeLog,v
retrieving revision 1.329
retrieving revision 1.330
diff -u -d -r1.329 -r1.330
--- ChangeLog	6 Dec 2004 07:36:34 -0000	1.329
+++ ChangeLog	6 Dec 2004 08:09:29 -0000	1.330
@@ -1,5 +1,7 @@
 2004-12-05  Brian Warner  <warner at lothar.com>
 
+	* NEWS: update for stuff since last release
+
 	* buildbot/master.py (DebugPerspective.attached): return 'self', to
 	match the maybeDeferred change in Dispatcher.requestAvatar
 	* buildbot/changes/pb.py (ChangePerspective.attached): same

Index: NEWS
===================================================================
RCS file: /cvsroot/buildbot/buildbot/NEWS,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- NEWS	23 Nov 2004 11:18:40 -0000	1.33
+++ NEWS	6 Dec 2004 08:09:30 -0000	1.34
@@ -1,5 +1,53 @@
 User visible changes in Buildbot.
 
+* Release ? (?)
+
+** new features
+
+It is now possible to interrupt a running build. Both the web page and the
+IRC bot feature 'stop build' commands, which can be used to interrupt the
+current BuildStep and accelerate the termination of the overall Build. The
+status reporting for these still leaves something to be desired (an
+'interrupt' event is pushed into the column, and the reason for the interrupt
+is added to a pseudo-logfile for the step that was stopped, but if you only
+look at the top-level status it appears that the build failed on its own).
+
+Builds are also halted if the connection to the buildmaster is lost.
+
+** minor new features
+
+The IRC log bot now reports ETA times in a MMSS format like "2m45s" instead
+of the clunky "165 seconds".
+
+** bug fixes
+
+*** Slave Disconnect
+
+Slave disconnects should be handled better now: the current build should be
+abandoned properly. Earlier versions could get into weird states where the
+build failed to finish, clogging the builder forever (or at least until the
+buildmaster was restarted).
+
+In addition, there are weird network conditions which could cause a
+buildslave to attempt to connect twice to the same buildmaster. This can
+happen when the slave is sending large logfiles over a slow link, while using
+short keepalive timeouts. The buildmaster has been fixed to allow the second
+connection attempt to take precedence over the first, so that the older
+connection is jettisoned to make way for the newer one. This is half of the
+fix, the other will involve fixing the slave to avoid the double-connect
+situation in the first place.
+
+*** Large Logfiles
+
+The web page rendering code has been fixed to deliver large logfiles in
+pieces, using a producer/consumer apparatus. This avoids the large spike in
+memory consumption when the log file body was linearized into a single string
+and then buffered in the socket's application-side transmit buffer. This
+should also avoid the 640k single-string limit for web.distrib servers that
+could be hit by large (>640k) logfiles.
+
+
+
 * Release 0.6.1 (23 Nov 2004)
 
 ** win32 improvements/bugfixes