The GUMP website incorrectly specifies the times that GUMP builds run on the various machines. Almost all of them run overnight, which makes it very difficult to do quicker test/fix for GUMP entries.
Here is what I have observed:
Machine | Build Time --------------------------------------------+------------- http://cvs.apache.org/builds/gump/latest/ | 12:00am (midnight) http://nagoya.apache.org/~rubys/gump/ | 8:00am http://gump.covalent.net/log/index.html | 7:00pm http://gump.cocoondev.org/ | 1:00am http://lsd.student.utwente.nl/gump/ | 6:00am
The web site advertises:
Machine | Build Time --------------------------------------------+------------- http://cvs.apache.org/builds/gump/latest/ | 11:00pm http://nagoya.apache.org/~rubys/gump/ | 7:00am http://gump.covalent.net/log/index.html | 3:00pm http://gump.cocoondev.org/ | 6:00pm http://lsd.student.utwente.nl/gump/ | 8:00pm
(All times reported EST)
The major problem is that only two of these machines are reported accurately, and the timings are not spaced nicely enough to make it nicer to use.
There are 5 different machines, wich means we could theorhetically set these to go off on 5 hour intervals. Also, it would help if the time was reported all in one time zone. The first list is based on the times reported by the server.
Can GUMP be forced to use GMT to report all times? That way it provides better auditing for those of us who really count on those mid-afternoon Gump runs.
The best schedule that I could think of is:
00:00 (midnight) 05:00 (5am) 10:00 (10am) 15:00 (3pm) 20:00 (8pm)
Of course this is all up to the various owners of the boxes to cooperatively schedule. Having two gump runs in the middle of the day is a big plus IMO.
How would we go about organizing this? There is a big hole in the middle of the day.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
