------------------------------------------------------------------------- $ ./ubersmoke Polling smokeboxes for status... Synchronising with the sickle_proxy repository...
Scheduling smoke tests
curly: starting smoke test for perl 5.8.x, change number 20558
Smoke running
fubar: starting smoke test for perl 5.8.x, change number 20558
Smoke runningUberSmoke status at 08/08/2003 12:22:47 BST -------------------------------------------
Repository branch for perl 5.6.x Latest change number is 19718 Repository branch for perl 5.8.x Latest change number is 20558 Repository branch for perl 5.9.x Latest change number is 20560
larry is UP [SunOS larry 5.6 Generic_105181-34 sun4u sparc SUNW,Ultra-1]
Perl 5.8.x smoke is running
change number 20558 started on 08/08/2003 10:53:05 BST
Perl 5.9.x smoke is not running
Perl 5.6.x smoke is not running
moe is UP [SunOS moe 5.7 Generic_106541-25 sun4u sparc SUNW,Ultra-1]
Perl 5.8.x smoke is running
change number 20558 started on 08/08/2003 11:36:48 BST
Perl 5.9.x smoke is not running
Perl 5.6.x smoke is not running
curly is UP [SunOS curly 5.8 Generic_108528-23 sun4u sparc SUNW,Ultra-1]
Perl 5.8.x smoke is running
change number 20558 started on 08/08/2003 12:22:37 BST
Perl 5.9.x smoke is not running
Perl 5.6.x smoke is not running
fubar is UP [SunOS fubar 5.9 Generic_112233-07 sun4u sparc SUNW,Ultra-30]
Perl 5.8.x smoke is running
change number 20558 started on 08/08/2003 12:22:47 BST
Perl 5.9.x smoke is not running
Perl 5.6.x smoke is not running
-------------------------------------------------------------------------There are 4 sparc boxes running Solaris 2.6, 2.7, 2.8 & 2.9 - I may add a Solaris 10 one if I can find a spare machine. The ubersmoke script syncs the local copy of then perl repository and kicks off smokes on each of the 4 boxes if a) the repository has been updated and b) they aren't running a smoke already. The smokes are done in priority order, i.e. 5.8.x is preferred over 5.6.x is preferred over 5.9.x. Other schemes are possible, e.g. prefer the version with the greatest number of changes between the last smoke and the current repository - I'm open to suggestions. I expect these tests to take several days, the machines are really old 167MHz Ultra1's. I'll forward the results as they arrive. I'll also figure out some interim way of archiving the log files - I'll probably hack the Test::Smoke generated shell scripts to use the change number as part of the log filename.
-- Alan Burlison --
