I wonder if the Hudson project has any
advise/opinions on if an upgrade to Hudson would help reduce "interference"?
We are on a pretty old version.
- Should we Upgrade to Hudson 3.1.0?
Put another way, if we can't run a Mac Machine and a Windows
Machine as two independent slaves ... Hudson is not doing us much good
And to put yet another way ... if we had to run them serially
... our 6 to 8 hour test suites would seldom ever finish! :(
Denis Roy <denis.roy@xxxxxxxxxxx>
10/24/2013 08:46 AM
Shared Hudson instance reacts extremly slow
On 10/24/2013 02:40 AM, David M Williams wrote:
> I'm not sure it's wise to have
the ep4-inut-mac64 and ep4-unit-win32 jobs both be running at the same
I don't understand why this would be the case. The are separate physical
They are separate physical machines, but they are slaves. As I understand
it, slave delegation means the master is tossing Java objects around to
the slave for execution, so the master doesn't just sit idle while the
slave does its work.
But, back to the point of original topic,
it is not so much that a "sudden restart caused [us] some grief"
but the fact that there is no clue or announcement that it was done, which
is the point of Bug
So here we are, providing some clues.
Matt is restarting the master now, since it has been tied up all night.
I think it would be a great idea to avoid running both of those jobs
at the same time to see if it takes care of the non-response issue.
I'm not sure it's wise to have the ep4-inut-mac64 and ep4-unit-win32 jobs
both be running at the same time, though....
I see 36m left for win32, 2h05 left for Mac.
On 10/23/2013 04:57 PM, Denis Roy wrote:
I think the Windows/Mac tests seriously affect the master performance.
Last time we've seen this David was running tests and our sudden
restart caused him some grief.
On 10/23/2013 04:24 PM, Denis Roy wrote:
Yep, but it's running eight builds right now, so we don't want to restart
Hang in there...
On 10/23/2013 04:17 PM, Tom Schindl wrote:
... anyoneelse seeing hudson being extremly slow?