syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <elecha...@gmail.com>
Subject Re: failures in Jenkins
Date Wed, 02 May 2012 16:36:55 GMT
Le 5/2/12 5:12 PM, Francesco Chicchiriccò a écrit :
> On 02/05/2012 16:59, Emmanuel Lécharny wrote:
>> Hi guys
>> it seems you have frequent failures in jenkins, due to a Tomcat port 
>> already used ( 
>> https://builds.apache.org/job/Syncope-windows/ws/core/target/log/cargo-output.log)
>
> The port already used are 9082, used by the external TCP H2 instance 
> and 9080, used by Tomcat.
>
>> Selecting a fixed port (9080) to run tests is not the right approach, 
>> you should use 0 intsead. See 
>> http://olamy.blogspot.fr/2012/01/unit-tests-with-embeded-tomcat.html
>
> This would require a considerable change in POMs since we are not 
> using the tomcat plugin, but the cargo plugin.
>
>> Also, check that you are correctly closing all the running instances 
>> even if the tests are failing, otherwise you'll piss off the Jenkins 
>> admin very quickly (it's really important if you use port 0 instead 
>> of a fixed port)...
>
> We never had such issues on Linux builds.
>
> Anyway, I'll try to contact someone from INFRA in order to clean up 
> the workspace.

Contact Olivier Lamy, who is managing the jenkins instances. We talked a 
bit about the issue, but as I know little (well, 'nothing' would be more 
appropriate ;) about Syncope itself, I wasn't able to give him enough 
context...



-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com


Mime
View raw message