You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by je...@cloudstack.org on 2014/11/12 05:56:50 UTC

Build failed in Jenkins: simulator-singlerun #602

See <http://jenkins.buildacloud.org/job/simulator-singlerun/602/changes>

Changes:

[mike.tutkowski] Add properties file in same folder as template

------------------------------------------
[...truncated 8814 lines...]
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
[INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:12.293s
[INFO] Finished at: Tue Nov 11 23:52:22 EST 2014
[INFO] Final Memory: 42M/171M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "simulator" could not be activated because it does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer ---
log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists `simulator`
============> Running query: create database `simulator`
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud'
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql>
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
[INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 24.518s
[INFO] Finished at: Tue Nov 11 23:52:49 EST 2014
[INFO] Final Memory: 41M/228M
[INFO] ------------------------------------------------------------------------
[simulator-singlerun] $ /bin/bash -x /tmp/hudson4502740428902339564.sh
+ jps -l
+ grep -q Launcher
+ rm -f xunit.xml
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=13629
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=6
+ '[' 6 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=7
+ '[' 7 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=8
+ '[' 8 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=9
+ '[' 9 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=10
+ '[' 10 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=11
+ '[' 11 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=12
+ '[' 12 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=13
+ '[' 13 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=14
+ '[' 14 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=15
+ '[' 15 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=16
+ '[' 16 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=17
+ '[' 17 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=18
+ '[' 18 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=19
+ '[' 19 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=20
+ '[' 20 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=21
+ '[' 21 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=22
+ '[' 22 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=23
+ '[' 23 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=24
+ '[' 24 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=25
+ '[' 25 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=26
+ '[' 26 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=27
+ '[' 27 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ break
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ echo Started OK pid 13629
Started OK pid 13629
+ sleep 20
+ export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg
/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)

==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Nov_11_2014_23_55_29_YMY7Z7. All logs will be available here ====

=== TestClient Creation Failed===
+ sleep 60
+ /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke

==== Marvin Init Started ====

=== Marvin Parse Config Successful ===

=== Marvin Setting TestData Successful===

==== Log Folder Path: /tmp//MarvinLogs//Nov_11_2014_23_56_32_L4XWUC. All logs will be available here ====

=== Marvin Init Logging Successful===

==== Marvin Init Failed ====

Starting Marvin Failed, exiting. Please Check
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.861s
[INFO] Finished at: Tue Nov 11 23:56:39 EST 2014
[INFO] Final Memory: 25M/153M
[INFO] ------------------------------------------------------------------------
+ sleep 10
+ kill -KILL 13629
/tmp/hudson4502740428902339564.sh: line 44: kill: (13629) - No such process
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'.
[xUnit] [ERROR] - The result file '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> for the metric 'JUnit' is not valid. The result file has been skipped.
[xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE

Jenkins build is back to normal : simulator-singlerun #607

Posted by je...@cloudstack.org.
See <http://jenkins.buildacloud.org/job/simulator-singlerun/607/changes>

Re: StatsCollector change 840c2f is breaking simulator run (Re: Build failed in Jenkins: simulator-singlerun #606)

Posted by Wido den Hollander <wi...@widodh.nl>.

On 11/12/2014 02:38 PM, Leo Simons wrote:
> Hey Wido,
> 
> The simulator build on jenkins is failing to start the cloudstack server with
> 

My apologies, that slipped past my tests. I added a extra check with
95daa14e2ac4bec09cfad890220e98eaa577c134

That should fix it.

Wido

> [ERROR] Failed startup of context org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@43925b62{/client,/home/jenkins/slave/workspace/team_tkt/cloudstack/simul
> ator-master/client/target/generated-webapp}
> java.lang.NullPointerException
>         at com.cloud.server.StatsCollector.init(StatsCollector.java:269)
>         at com.cloud.server.StatsCollector.start(StatsCollector.java:247)
>         at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$1.with(CloudStackExtendedLifeCycle.java:75)
>         at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153)
>         at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.startBeans(CloudStackExtendedLifeCycle.java:72)
>         at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycleStart.run(CloudStackExtendedLifeCycleStart.java:46)
>         at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$1.with(DefaultModuleDefinitionSet.java:105)
>         at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
>         at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
>         at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
>         at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
>         at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.startContexts(DefaultModuleDefinitionSet.java:97)
>         at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:80)
>         at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
>         at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70)
>         at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:57)
>         at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:61)
>         at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52)
>         at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
>         at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> 
> (well, I can't see jenkins.buildacloud.org workspace, but that's what we get on our replica of this build).
> 
> which is at brand new line
> 
>   https://github.com/apache/cloudstack/commit/840c2fda852b86f51245a31e7cd91cdb0ad4bf49#diff-5a9d445f9ba381a581f4596d4887c8d5R269
> 
> that I think you wrote a while back and pushed a day ago. My guess is uri.getScheme() returns null because stats.output.uri is an empty string?
> 
>   https://github.com/apache/cloudstack/commit/840c2fda852b86f51245a31e7cd91cdb0ad4bf49#diff-3203f16e21aa67a34b79266395d7be7cR2062
> 
> can you take a look?
> 
> 
> cheers,
> 
> 
> Leo
> 
> 
> On Nov 12, 2014, at 11:09 AM, jenkins@cloudstack.org wrote:
> 
>> See <http://jenkins.buildacloud.org/job/simulator-singlerun/606/>
>>
>> ------------------------------------------
>> [...truncated 8812 lines...]
>> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/developer-prefill.sql>
>> ========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
>> [INFO] 
>> [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
>> [INFO] 
>> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
>> [INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time: 1:59.155s
>> [INFO] Finished at: Wed Nov 12 05:04:50 EST 2014
>> [INFO] Final Memory: 42M/159M
>> [INFO] ------------------------------------------------------------------------
>> [WARNING] The requested profile "simulator" could not be activated because it does not exist.
>> [simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
>> [INFO] Scanning for projects...
>> [INFO]                                                                         
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
>> [INFO] ------------------------------------------------------------------------
>> [INFO] 
>> [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
>> [INFO] Starting audit...
>> Audit done.
>>
>> [INFO] 
>> [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer ---
>> [WARNING] Ignoring missing properties file: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
>> [INFO] 
>> [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer ---
>> [INFO] 
>> [INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
>> [INFO] Executing tasks
>>
>> main:
>> [INFO] Executed tasks
>> [INFO] 
>> [INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>>
>> [INFO] 
>> [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
>> [INFO] Starting audit...
>> Audit done.
>>
>> [INFO] 
>> [INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<<
>> [INFO] 
>> [INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer ---
>> log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
>> log4j:WARN Please initialize the log4j system properly.
>> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
>> ========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
>> ========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud
>> ============> Running query: drop database if exists `simulator`
>> ============> Running query: create database `simulator`
>> ============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud'
>> ============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud'
>> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql>
>> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql>
>> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql>
>> ========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
>> [INFO] 
>> [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
>> [INFO] 
>> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
>> [INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time: 18.114s
>> [INFO] Finished at: Wed Nov 12 05:05:12 EST 2014
>> [INFO] Final Memory: 43M/185M
>> [INFO] ------------------------------------------------------------------------
>> [simulator-singlerun] $ /bin/bash -x /tmp/hudson1744104456574609116.sh
>> + jps -l
>> + grep -q Launcher
>> + rm -f xunit.xml
>> + echo ''
>> + rm -rf /tmp/MarvinLogs
>> + echo Check for initialization of the management server
>> Check for initialization of the management server
>> + COUNTER=0
>> + SERVER_PID=16523
>> + '[' 0 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
>> + sleep 5
>> + COUNTER=1
>> + '[' 1 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=2
>> + '[' 2 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=3
>> + '[' 3 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=4
>> + '[' 4 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=5
>> + '[' 5 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=6
>> + '[' 6 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=7
>> + '[' 7 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=8
>> + '[' 8 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=9
>> + '[' 9 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=10
>> + '[' 10 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=11
>> + '[' 11 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=12
>> + '[' 12 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=13
>> + '[' 13 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=14
>> + '[' 14 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=15
>> + '[' 15 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=16
>> + '[' 16 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=17
>> + '[' 17 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=18
>> + '[' 18 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=19
>> + '[' 19 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=20
>> + '[' 20 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=21
>> + '[' 21 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=22
>> + '[' 22 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=23
>> + '[' 23 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=24
>> + '[' 24 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=25
>> + '[' 25 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + sleep 5
>> + COUNTER=26
>> + '[' 26 -lt 44 ']'
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + break
>> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>> + echo Started OK pid 16523
>> Started OK pid 16523
>> + sleep 20
>> + export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
>> + PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
>> + python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg
>> /usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
>>  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
>>
>> ==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_05_07_46_ZHMXMR. All logs will be available here ====
>>
>> === TestClient Creation Failed===
>> + sleep 60
>> + /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke
>>
>> ==== Marvin Init Started ====
>>
>> === Marvin Parse Config Successful ===
>>
>> === Marvin Setting TestData Successful===
>>
>> ==== Log Folder Path: /tmp//MarvinLogs//Nov_12_2014_05_08_48_SYEWES. All logs will be available here ====
>>
>> === Marvin Init Logging Successful===
>>
>> ==== Marvin Init Failed ====
>>
>> Starting Marvin Failed, exiting. Please Check
>> + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop
>> [INFO] Scanning for projects...
>> [INFO]                                                                         
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT
>> [INFO] ------------------------------------------------------------------------
>> [INFO] 
>> [INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui ---
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time: 4.669s
>> [INFO] Finished at: Wed Nov 12 05:08:55 EST 2014
>> [INFO] Final Memory: 25M/154M
>> [INFO] ------------------------------------------------------------------------
>> + sleep 10
>> + kill -KILL 16523
>> /tmp/hudson1744104456574609116.sh: line 44: kill: (16523) - No such process
>> [locks-and-latches] Releasing all the locks
>> [locks-and-latches] All the locks released
>> [xUnit] [INFO] - Starting to record.
>> [xUnit] [INFO] - Processing JUnit
>> [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'.
>> [xUnit] [ERROR] - The result file '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> for the metric 'JUnit' is not valid. The result file has been skipped.
>> [xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated.
>> [xUnit] [INFO] - There are errors when processing test results.
>> [xUnit] [INFO] - Skipping tests recording.
>> [xUnit] [INFO] - Stop build.
>> Build step 'Publish xUnit test result report' changed build result to FAILURE
>

StatsCollector change 840c2f is breaking simulator run (Re: Build failed in Jenkins: simulator-singlerun #606)

Posted by Leo Simons <LS...@schubergphilis.com>.
Hey Wido,

The simulator build on jenkins is failing to start the cloudstack server with

[ERROR] Failed startup of context org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@43925b62{/client,/home/jenkins/slave/workspace/team_tkt/cloudstack/simul
ator-master/client/target/generated-webapp}
java.lang.NullPointerException
        at com.cloud.server.StatsCollector.init(StatsCollector.java:269)
        at com.cloud.server.StatsCollector.start(StatsCollector.java:247)
        at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$1.with(CloudStackExtendedLifeCycle.java:75)
        at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153)
        at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.startBeans(CloudStackExtendedLifeCycle.java:72)
        at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycleStart.run(CloudStackExtendedLifeCycleStart.java:46)
        at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$1.with(DefaultModuleDefinitionSet.java:105)
        at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
        at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
        at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
        at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
        at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.startContexts(DefaultModuleDefinitionSet.java:97)
        at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:80)
        at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
        at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70)
        at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:57)
        at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:61)
        at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52)
        at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
        at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)

(well, I can't see jenkins.buildacloud.org workspace, but that's what we get on our replica of this build).

which is at brand new line

  https://github.com/apache/cloudstack/commit/840c2fda852b86f51245a31e7cd91cdb0ad4bf49#diff-5a9d445f9ba381a581f4596d4887c8d5R269

that I think you wrote a while back and pushed a day ago. My guess is uri.getScheme() returns null because stats.output.uri is an empty string?

  https://github.com/apache/cloudstack/commit/840c2fda852b86f51245a31e7cd91cdb0ad4bf49#diff-3203f16e21aa67a34b79266395d7be7cR2062

can you take a look?


cheers,


Leo


On Nov 12, 2014, at 11:09 AM, jenkins@cloudstack.org wrote:

> See <http://jenkins.buildacloud.org/job/simulator-singlerun/606/>
> 
> ------------------------------------------
> [...truncated 8812 lines...]
> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/developer-prefill.sql>
> ========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
> [INFO] 
> [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
> [INFO] 
> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
> [INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:59.155s
> [INFO] Finished at: Wed Nov 12 05:04:50 EST 2014
> [INFO] Final Memory: 42M/159M
> [INFO] ------------------------------------------------------------------------
> [WARNING] The requested profile "simulator" could not be activated because it does not exist.
> [simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
> [INFO] Scanning for projects...
> [INFO]                                                                         
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO] 
> [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
> [INFO] Starting audit...
> Audit done.
> 
> [INFO] 
> [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer ---
> [WARNING] Ignoring missing properties file: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer ---
> [INFO] 
> [INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
> [INFO] Executing tasks
> 
> main:
> [INFO] Executed tasks
> [INFO] 
> [INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>>
> [INFO] 
> [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
> [INFO] Starting audit...
> Audit done.
> 
> [INFO] 
> [INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<<
> [INFO] 
> [INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer ---
> log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> ========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
> ========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud
> ============> Running query: drop database if exists `simulator`
> ============> Running query: create database `simulator`
> ============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud'
> ============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud'
> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql>
> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql>
> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql>
> ========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
> [INFO] 
> [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
> [INFO] 
> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
> [INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 18.114s
> [INFO] Finished at: Wed Nov 12 05:05:12 EST 2014
> [INFO] Final Memory: 43M/185M
> [INFO] ------------------------------------------------------------------------
> [simulator-singlerun] $ /bin/bash -x /tmp/hudson1744104456574609116.sh
> + jps -l
> + grep -q Launcher
> + rm -f xunit.xml
> + echo ''
> + rm -rf /tmp/MarvinLogs
> + echo Check for initialization of the management server
> Check for initialization of the management server
> + COUNTER=0
> + SERVER_PID=16523
> + '[' 0 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
> + sleep 5
> + COUNTER=1
> + '[' 1 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=2
> + '[' 2 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=3
> + '[' 3 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=4
> + '[' 4 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=5
> + '[' 5 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=6
> + '[' 6 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=7
> + '[' 7 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=8
> + '[' 8 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=9
> + '[' 9 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=10
> + '[' 10 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=11
> + '[' 11 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=12
> + '[' 12 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=13
> + '[' 13 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=14
> + '[' 14 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=15
> + '[' 15 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=16
> + '[' 16 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=17
> + '[' 17 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=18
> + '[' 18 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=19
> + '[' 19 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=20
> + '[' 20 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=21
> + '[' 21 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=22
> + '[' 22 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=23
> + '[' 23 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=24
> + '[' 24 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=25
> + '[' 25 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + sleep 5
> + COUNTER=26
> + '[' 26 -lt 44 ']'
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + break
> + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
> + echo Started OK pid 16523
> Started OK pid 16523
> + sleep 20
> + export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
> + PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
> + python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg
> /usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
>  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
> 
> ==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_05_07_46_ZHMXMR. All logs will be available here ====
> 
> === TestClient Creation Failed===
> + sleep 60
> + /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke
> 
> ==== Marvin Init Started ====
> 
> === Marvin Parse Config Successful ===
> 
> === Marvin Setting TestData Successful===
> 
> ==== Log Folder Path: /tmp//MarvinLogs//Nov_12_2014_05_08_48_SYEWES. All logs will be available here ====
> 
> === Marvin Init Logging Successful===
> 
> ==== Marvin Init Failed ====
> 
> Starting Marvin Failed, exiting. Please Check
> + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop
> [INFO] Scanning for projects...
> [INFO]                                                                         
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO] 
> [INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui ---
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4.669s
> [INFO] Finished at: Wed Nov 12 05:08:55 EST 2014
> [INFO] Final Memory: 25M/154M
> [INFO] ------------------------------------------------------------------------
> + sleep 10
> + kill -KILL 16523
> /tmp/hudson1744104456574609116.sh: line 44: kill: (16523) - No such process
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> [xUnit] [INFO] - Starting to record.
> [xUnit] [INFO] - Processing JUnit
> [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'.
> [xUnit] [ERROR] - The result file '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> for the metric 'JUnit' is not valid. The result file has been skipped.
> [xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated.
> [xUnit] [INFO] - There are errors when processing test results.
> [xUnit] [INFO] - Skipping tests recording.
> [xUnit] [INFO] - Stop build.
> Build step 'Publish xUnit test result report' changed build result to FAILURE

Build failed in Jenkins: simulator-singlerun #606

Posted by je...@cloudstack.org.
See <http://jenkins.buildacloud.org/job/simulator-singlerun/606/>

------------------------------------------
[...truncated 8812 lines...]
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/developer-prefill.sql>
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
[INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:59.155s
[INFO] Finished at: Wed Nov 12 05:04:50 EST 2014
[INFO] Final Memory: 42M/159M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "simulator" could not be activated because it does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer ---
log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists `simulator`
============> Running query: create database `simulator`
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud'
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql>
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
[INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.114s
[INFO] Finished at: Wed Nov 12 05:05:12 EST 2014
[INFO] Final Memory: 43M/185M
[INFO] ------------------------------------------------------------------------
[simulator-singlerun] $ /bin/bash -x /tmp/hudson1744104456574609116.sh
+ jps -l
+ grep -q Launcher
+ rm -f xunit.xml
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=16523
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=6
+ '[' 6 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=7
+ '[' 7 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=8
+ '[' 8 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=9
+ '[' 9 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=10
+ '[' 10 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=11
+ '[' 11 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=12
+ '[' 12 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=13
+ '[' 13 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=14
+ '[' 14 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=15
+ '[' 15 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=16
+ '[' 16 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=17
+ '[' 17 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=18
+ '[' 18 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=19
+ '[' 19 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=20
+ '[' 20 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=21
+ '[' 21 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=22
+ '[' 22 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=23
+ '[' 23 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=24
+ '[' 24 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=25
+ '[' 25 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=26
+ '[' 26 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ break
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ echo Started OK pid 16523
Started OK pid 16523
+ sleep 20
+ export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg
/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)

==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_05_07_46_ZHMXMR. All logs will be available here ====

=== TestClient Creation Failed===
+ sleep 60
+ /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke

==== Marvin Init Started ====

=== Marvin Parse Config Successful ===

=== Marvin Setting TestData Successful===

==== Log Folder Path: /tmp//MarvinLogs//Nov_12_2014_05_08_48_SYEWES. All logs will be available here ====

=== Marvin Init Logging Successful===

==== Marvin Init Failed ====

Starting Marvin Failed, exiting. Please Check
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.669s
[INFO] Finished at: Wed Nov 12 05:08:55 EST 2014
[INFO] Final Memory: 25M/154M
[INFO] ------------------------------------------------------------------------
+ sleep 10
+ kill -KILL 16523
/tmp/hudson1744104456574609116.sh: line 44: kill: (16523) - No such process
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'.
[xUnit] [ERROR] - The result file '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> for the metric 'JUnit' is not valid. The result file has been skipped.
[xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE

Build failed in Jenkins: simulator-singlerun #605

Posted by je...@cloudstack.org.
See <http://jenkins.buildacloud.org/job/simulator-singlerun/605/changes>

Changes:

[wido] CLOUDSTACK-3383: Fetch CPU utilization more reliable.

------------------------------------------
[...truncated 8822 lines...]
[INFO] Final Memory: 42M/164M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "simulator" could not be activated because it does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer ---
log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists `simulator`
============> Running query: create database `simulator`
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud'
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql>
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
[INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20.888s
[INFO] Finished at: Wed Nov 12 04:42:46 EST 2014
[INFO] Final Memory: 41M/162M
[INFO] ------------------------------------------------------------------------
[simulator-singlerun] $ /bin/bash -x /tmp/hudson3834564774054683583.sh
+ jps -l
+ grep -q Launcher
+ rm -f xunit.xml
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=9918
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=6
+ '[' 6 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=7
+ '[' 7 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=8
+ '[' 8 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=9
+ '[' 9 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=10
+ '[' 10 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=11
+ '[' 11 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=12
+ '[' 12 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=13
+ '[' 13 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=14
+ '[' 14 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=15
+ '[' 15 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=16
+ '[' 16 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=17
+ '[' 17 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=18
+ '[' 18 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=19
+ '[' 19 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=20
+ '[' 20 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=21
+ '[' 21 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=22
+ '[' 22 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=23
+ '[' 23 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=24
+ '[' 24 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=25
+ '[' 25 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=26
+ '[' 26 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=27
+ '[' 27 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=28
+ '[' 28 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=29
+ '[' 29 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ break
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ echo Started OK pid 9918
Started OK pid 9918
+ sleep 20
+ export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg
/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)

==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_04_45_36_WBAG4P. All logs will be available here ====

=== TestClient Creation Failed===
+ sleep 60
+ /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke

==== Marvin Init Started ====

=== Marvin Parse Config Successful ===

=== Marvin Setting TestData Successful===

==== Log Folder Path: /tmp//MarvinLogs//Nov_12_2014_04_46_38_AIIE41. All logs will be available here ====

=== Marvin Init Logging Successful===

==== Marvin Init Failed ====

Starting Marvin Failed, exiting. Please Check
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.460s
[INFO] Finished at: Wed Nov 12 04:46:45 EST 2014
[INFO] Final Memory: 25M/114M
[INFO] ------------------------------------------------------------------------
+ sleep 10
+ kill -KILL 9918
/tmp/hudson3834564774054683583.sh: line 44: kill: (9918) - No such process
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'.
[xUnit] [ERROR] - The result file '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> for the metric 'JUnit' is not valid. The result file has been skipped.
[xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
Build step 'Publish xUnit test result report' changed build result to FAILURE

Build failed in Jenkins: simulator-singlerun #604

Posted by je...@cloudstack.org.
See <http://jenkins.buildacloud.org/job/simulator-singlerun/604/>

------------------------------------------
[...truncated 8849 lines...]

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer ---
log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists `simulator`
============> Running query: create database `simulator`
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud'
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql>
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
[INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.777s
[INFO] Finished at: Wed Nov 12 00:42:29 EST 2014
[INFO] Final Memory: 43M/194M
[INFO] ------------------------------------------------------------------------
[simulator-singlerun] $ /bin/bash -x /tmp/hudson7202576239856259299.sh
+ grep -q Launcher
+ jps -l
+ rm -f xunit.xml
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=27055
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=6
+ '[' 6 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=7
+ '[' 7 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=8
+ '[' 8 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=9
+ '[' 9 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=10
+ '[' 10 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=11
+ '[' 11 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=12
+ '[' 12 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=13
+ '[' 13 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=14
+ '[' 14 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=15
+ '[' 15 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=16
+ '[' 16 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=17
+ '[' 17 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=18
+ '[' 18 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=19
+ '[' 19 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=20
+ '[' 20 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=21
+ '[' 21 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=22
+ '[' 22 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=23
+ '[' 23 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=24
+ '[' 24 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=25
+ '[' 25 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=26
+ '[' 26 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=27
+ '[' 27 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=28
+ '[' 28 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=29
+ '[' 29 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=30
+ '[' 30 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=31
+ '[' 31 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=32
+ '[' 32 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=33
+ '[' 33 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=34
+ '[' 34 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ break
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ echo Started OK pid 27055
Started OK pid 27055
+ sleep 20
+ export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg
/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)

==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_00_45_44_B15B5G. All logs will be available here ====

==== Deploy DC Started ====

=== Data Center Settings are dumped to /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_00_45_44_B15B5G/dc_entries.obj===

====Deploy DC Successful=====
+ sleep 60
+ /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke

==== Marvin Init Started ====

=== Marvin Parse Config Successful ===

=== Marvin Setting TestData Successful===

==== Log Folder Path: /tmp//MarvinLogs//Nov_12_2014_00_49_36_QQ32C3. All logs will be available here ====

=== Marvin Init Logging Successful===

==== Marvin Init Successful ====
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.893s
[INFO] Finished at: Wed Nov 12 00:49:58 EST 2014
[INFO] Final Memory: 25M/119M
[INFO] ------------------------------------------------------------------------
+ sleep 10
+ kill -KILL 27055
/tmp/hudson7202576239856259299.sh: line 44: kill: (27055) - No such process
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'.
[xUnit] [INFO] - Converting '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> .
[xUnit] [INFO] - Check 'Failed Tests' threshold.
[xUnit] [INFO] - The total number of tests for this category exceeds the specified 'failure' threshold value.
[xUnit] [INFO] - Setting the build status to FAILURE
[xUnit] [INFO] - Stopping recording.
Build step 'Publish xUnit test result report' changed build result to FAILURE

Build failed in Jenkins: simulator-singlerun #603

Posted by je...@cloudstack.org.
See <http://jenkins.buildacloud.org/job/simulator-singlerun/603/changes>

Changes:

[koushik] CLOUDSTACK-7886: cloudstackoperations like deployvm,deleteNW are failing if CS fail to contact rabbit mq server. This is happening in case of Async API calls.

------------------------------------------
[...truncated 8874 lines...]
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer ---
log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override>
========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists `simulator`
============> Running query: create database `simulator`
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud'
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql>
========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql>
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer ---
[INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 28.795s
[INFO] Finished at: Wed Nov 12 00:15:43 EST 2014
[INFO] Final Memory: 42M/204M
[INFO] ------------------------------------------------------------------------
[simulator-singlerun] $ /bin/bash -x /tmp/hudson6395764887189000704.sh
+ jps -l
+ grep -q Launcher
+ rm -f xunit.xml
+ echo ''
+ rm -rf /tmp/MarvinLogs
+ echo Check for initialization of the management server
Check for initialization of the management server
+ COUNTER=0
+ SERVER_PID=20253
+ '[' 0 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run
+ sleep 5
+ COUNTER=1
+ '[' 1 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=2
+ '[' 2 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=3
+ '[' 3 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=4
+ '[' 4 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=5
+ '[' 5 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=6
+ '[' 6 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=7
+ '[' 7 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=8
+ '[' 8 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=9
+ '[' 9 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=10
+ '[' 10 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=11
+ '[' 11 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=12
+ '[' 12 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=13
+ '[' 13 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=14
+ '[' 14 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=15
+ '[' 15 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=16
+ '[' 16 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=17
+ '[' 17 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=18
+ '[' 18 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=19
+ '[' 19 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=20
+ '[' 20 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=21
+ '[' 21 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=22
+ '[' 22 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=23
+ '[' 23 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=24
+ '[' 24 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=25
+ '[' 25 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=26
+ '[' 26 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=27
+ '[' 27 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=28
+ '[' 28 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=29
+ '[' 29 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ sleep 5
+ COUNTER=30
+ '[' 30 -lt 44 ']'
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ break
+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
+ echo Started OK pid 20253
Started OK pid 20253
+ sleep 20
+ export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin>
+ python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg
/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)

==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_00_18_37_3RUM3W. All logs will be available here ====

==== Deploy DC Started ====

=== Data Center Settings are dumped to /tmp//MarvinLogs//DeployDataCenter__Nov_12_2014_00_18_37_3RUM3W/dc_entries.obj===

====Deploy DC Successful=====
+ sleep 60
+ /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke

==== Marvin Init Started ====

=== Marvin Parse Config Successful ===

=== Marvin Setting TestData Successful===

==== Log Folder Path: /tmp//MarvinLogs//Nov_12_2014_00_22_31_COK8X8. All logs will be available here ====

=== Marvin Init Logging Successful===

==== Marvin Init Successful ====
+ mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.541s
[INFO] Finished at: Wed Nov 12 00:22:54 EST 2014
[INFO] Final Memory: 25M/117M
[INFO] ------------------------------------------------------------------------
+ sleep 10
+ kill -KILL 20253
/tmp/hudson6395764887189000704.sh: line 44: kill: (20253) - No such process
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'.
[xUnit] [INFO] - Converting '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> .
[xUnit] [INFO] - Check 'Failed Tests' threshold.
[xUnit] [INFO] - The total number of tests for this category exceeds the specified 'failure' threshold value.
[xUnit] [INFO] - Setting the build status to FAILURE
[xUnit] [INFO] - Stopping recording.
Build step 'Publish xUnit test result report' changed build result to FAILURE