Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and Outlook at Juno M1 +0

Hudson (or, something) has a habit of hanging SCM polling threads, and then, eventually, Hudson runs out of them and polls no more (along with other complications, such as getting stale content, even though we use ":local:" in our configuration) [1] [2] [3] The only cure I have heard of is to restart Hudson. Or, short term, to manually start your 'job', as you have done.

I'd say if not fixed/restarted by Monday noon (based on this note), to open a bugzilla for Eclipse's hudson admins. [4]

Thanks for noticing, and letting us know.


From:        Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>
To:        cross-project-issues-dev@xxxxxxxxxxx
Cc:        David M Williams/Raleigh/IBM@IBMUS
Date:        08/13/2011 10:06 AM
Subject:        Re: [cross-project-issues-dev] Status and Outlook at Juno M1 +0

Hi David,

On Saturday, August 13, 2011 01:03:34 AM David M Williams wrote:
> and one project, not surprisingly, has a tight coupling to JDT that will
> need some adjustment
> objectteams

Thanks for your understanding.

Now when updating our contribution I got a funny message in the
CVS polling log:

                Started on Aug 13, 2011 9:45:41 AM
                [juno.runAggregator] $ cvs -q -z0 -n update -PdC -D "Saturday, August 13,
2011 1:45:41 PM UTC"
                U objectteams.b3aggrcon
                Done. Took 2.7 sec
                No changes

Not all changes are changes? Or are CVS triggers disabled?


Back to the top