Home » Archived » Buckminster » Build is slow with buckminster 4.2
| Build is slow with buckminster 4.2 [message #1015544] |
Fri, 01 March 2013 08:28  |
 Vlad Dumitrescu
Messages: 431
Registered: July 2009
Location: Gothenburg |
Senior Member |
|
|
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] 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  |
|
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
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
| | | |
Goto Forum:
Current Time: Sat Apr 20 01:34:26 GMT 2024
Powered by FUDForum. Page generated in 0.02779 seconds |
] 
Search
Help
Register
Login
Home
