Stats pages stalled?

[Stefan Bodewig <bo...@apache.org>]

Hi,

the pages under
<http://brutus.apache.org/gump/public/gump_stats/index.html> all have
been created last Wednesday.  Is this expected?

Cheers

        Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Stats pages stalled?

[Stefan Bodewig <bo...@apache.org>]

On Tue, 7 Dec 2004, Adam R. B. Jack <aj...@apache.org> wrote:

> Stats only get generated upon the nightly official run (they were
> costing too much cycles back when we needed to save what we
> could). I see the crontab for "normal runs" has an entry for 21:00,
> and that the last Gump run took almost 3 hours (which is an inner
> timing, so maybe not exactly @ OS level). Maybe there is a small
> overlap.

There definitively is an overloap.  I can usually watch the 21:00 run
when it is going to the last few builds and we've been over 3 hours
for the last couple of days.

> This shows a 3 minute overlap. I'll tweak the crontab to give the
> official run a better chance.

Thanks

        Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Stats pages stalled?

["Adam R. B. Jack" <aj...@apache.org>]

> the pages under
> <http://brutus.apache.org/gump/public/gump_stats/index.html> all have
> been created last Wednesday.  Is this expected?

Nothing seems obvious, here are some thoughts:

Stats only get generated upon the nightly official run (they were costing
too much cycles back when we needed to save what we could). I see the
crontab for "normal runs" has an entry for 21:00, and that the last Gump run
took almost 3 hours (which is an inner timing, so maybe not exactly @ OS
level). Maybe there is a small overlap.

Ok, looking at:

    /usr/local/gump/public/gump/log/gump_runlog.txt

I see a bunch of these (for recent --official runs):

03 Dec 2004 21:00:01 : 16071 : Gump Start-up. Arguments [['gump.py', 'all']]
04 Dec 2004 00:00:02 : 27844 : Gump Start-up. Arguments [['gump.py', 'all',
'--official']]
04 Dec 2004 00:00:02 : 27844 : False Start. The lock file
[/home/gump/workspaces2/public/gump/gump.lock] exists, and is locked.
04 Dec 2004 00:03:35 : 16071 : Complete [0 svn:0,cvs:0,run:0]

This shows a 3 minute overlap. I'll tweak the crontab to give the official
run a better chance.

As we know, long term it'd nice to have a better "continuous Gump"
algorithm/scheduler.

regards

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org