> 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 don't understand why this would be the case. The are separate physical machines, right? And, the real mystery, to us in Platform, is why are the Mac tests are taking so long these days? They used to finish almost as fast as the Linux tests ... and Windows was the one that took "2 to 4 hours longer". Guess it wasn't the VM (Bug 419842) and wasn't the constant Bluetooth keyboard checking (Bug 419280) ... while it might, possibly, perhaps be something in our code, since it started about the same time that "Signing Mac executables" was started as a service from that machine, I have to ask one more question ... does that signing service call "sleep" or loop constantly looking for requests to sign something? That might tie up processors (doing nothing) that perhaps would slow down our tests ... and I've no idea how many processors that machine has, or even if its "sleep" function actually pauses a whole processor like I've been told other OSs do ... seems unlikely ... but no idea how its implemented (wasn't that C# was it :) ... I'm just grasping at straws, as to what would "suddenly" make those tests twice as slow. I might have to start using my own Mac for comparison :\ 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 417457. I think in years past, we've said that to restart Hudson any job that has over an hour left would be canceled, gracefully if possible, forcibly if not .... but that it should be "announced" in one form or another. I'd never expect you to wait for our long tests to complete. We can easily restart them (when Hudson is working) as long as there is some notification to wake me up from my nap. :) I would cancel the job myself but Hudson doesn't seem to be responding at all any more (502 "bad gateway" error). Thanks for the care and accommodation, though. Sincerely, From: Denis Roy <denis....@eclipse.org> To: cross-project-issues-dev@eclipse.org, Date: 10/23/2013 05:01 PM Subject: Re: [cross-project-issues-dev] Shared Hudson instance reacts extremly slow Sent by: cross-project-issues-dev-boun...@eclipse.org 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. Denis 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 it. Hang in there... Denis On 10/23/2013 04:17 PM, Tom Schindl wrote: ... anyoneelse seeing hudson being extremly slow? Tom _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<<image/png>>
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
