Build is slow with buckminster 4.2 [message #1015544] |
Fri, 01 March 2013 08:28  |
Eclipse User |
|
|
|
Hi!
I have updated my build server from buckminster 3.7 to 4.2 and besides problems with emma and jenkins (misunderstandings about the log format) I also noticed that it takes a lot longer to build with the new one!
One of the problems seems to be between the junit runs, where there is now a pause of about one minute, see log snippet below, but is not the only culprit.
Switching between the buckminster versions gives immediate and clear results (7 versus 19 minutes). Does anyone know what the problem might be and how to fix it?
best regards,
Vlad
09:15:45,483 I: (ErtsWatcher.java:73) : Backend '79825_jenkins_53b34_erlide' terminated with exit code 0.
INFO: junit '-l' 'org.erlide.testing/junit_core.launch' '-o' '/var/lib/jenkins/jobs/vlad_any/workspace/output/junit_result_core.xml' '--flatXML' '--terseXML' '--stderr' '--stdout'
09:16:50,067 F: (ErlangCore.java:77) : Starting CORE Thread[main,5,main]
[Updated on: Fri, 01 March 2013 08:28] by Moderator Report message to a moderator
|
|
|
Re: Build is slow with buckminster 4.2 [message #1016004 is a reply to message #1015544] |
Mon, 04 March 2013 15:15   |
Eclipse User |
|
|
|
Hi
can it be related to this buckminster's junit command line argument?
--maxTimeAwaitJunitReport
If your JUnit reports are huge (more than 200MB) then it may take some
time to work them up
and Buckminster finishes before the VM has had time to process the data.
The duration given with --maxTimeAwaitJunitReport will define the
maximum amount of time in seconds
to wait until the JUnit report should be created. The default is 10
seconds.
On 03/01/2013 09:28 AM, Vlad Dumitrescu wrote:
> Hi!
>
> I have updated my build server from buckminster 3.7 to 4.2 and besides
> problems with emma and jenkins (misunderstandings about the log format)
> I also noticed that it takes a lot longer to build with the new one!
>
> One of the problems seems to be between the junit runs, where there is
> now a pause of about one minute, see log snippet below, but is not the
> only culprit.
> Switching between the buckminster versions gives immediate and clear
> results (7 versus 19 minutes). Does anyone know what the problem might
> be and how to fix it?
>
> best regards,
> Vlad
>
> 09:15:45,483 I: (ErtsWatcher.java:73) : Backend
> '79825_jenkins_53b34_erlide' terminated with exit code 0.
> INFO: junit '-l' 'org.erlide.testing/junit_core.launch' '-o'
> '/var/lib/jenkins/jobs/vlad_any/workspace/output/junit_result_core.xml'
> '--flatXML' '--terseXML' '--stderr' '--stdout'
> 09:16:50,067 F: (ErlangCore.java:77) : Starting CORE Thread[main,5,main]
>
>
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
|
|
|
|
Re: Build is slow with buckminster 4.2 [message #1035888 is a reply to message #1016008] |
Sun, 07 April 2013 16:05   |
Eclipse User |
|
|
|
some follow-ups: I tried to run buckminster 4.2 headless with
-L DEBUG
and the whole build time is less than half!
For instance
without -L DEBUG: 11 minutes 41 seconds
with -L DEBUG : 4 minutes 40 seconds
I have both plain Junit tests, Plug-in Junit tests, and Swtbot tests in
this build...
On 03/04/2013 04:18 PM, Vlad Dumitrescu wrote:
> I'll check that out. Thanks Lorenzo!
>
> But there are also the one minute pauses between the junit runs, so
> there is something else too...
>
> /Vlad
>
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
|
|
|
|
Powered by
FUDForum. Page generated in 0.04156 seconds