Community
Participate
Working Groups
Trying to run an EMF build today, which normally takes about 20-30 mins including signing. Today, it's been stuck for 3 hours waiting for the signing to complete. Is there any way that there could be more than one genie or at least more than one concurrent process for signing? build.eclipse.org a 4-CPU server, right?
+1 What a great idea. I have encountered the same issue.
Done. Can someone test it out and let me know how it works?
(In reply to comment #2) > Done. Can someone test it out and let me know how it works? Will there be more than one /tmp/jarsigner to tail? I'm curious how to test this -- I can send several builds to the server at about the same time (perhaps a 2-minute offset?) and see if they wait for each other or run in parallel, but I'll need a log with timestamps to look at to ensure it's parallel, not serial.
"The build times started getting rough, The tiny build was tossed. If not for the courage of the webmasters, The Minnow would be lost. (The Minnow would be lost.)" ... Checking over some recent builds, signing generally takes 10-12 mins to run, and 5-6 mins to retrieve & manipulate. Average total over 4 builds: 16.75min. Running two EMF builds with a 2-minute overlap today, I saw build 1 take 13 and 10 mins and build 2 take 16 and 8 mins. Running two EMF builds with a 5-minute overlap today, I saw build 1 take 12 and 8 mins and build 2 take 12 and 10 mins. Average total over four builds: 22.25min Considering the overlap, a 33% increase in elapsed time (5 and a half minutes) seems tolerable, especially compared to the state before. (A three hour tour.) Thanks, skipper! ;-)
Thanks for opening this Nick. This will help us out a lot with our build times!
I just hope the quad-cpu server won't leave us stranded on an island after taking a beating =)
