cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nitin Mehta <Nitin.Me...@citrix.com>
Subject Re: Build failed in Jenkins: simulator-singlerun #485
Date Wed, 01 Oct 2014 21:40:42 GMT
Talluri/Hugo/Others with knowledge of Jenkins - Can you please look into
this and check why we keep getting false alarms because of issues on
Jenkins side ?

Thanks,
-Nitin

On 01/10/14 1:15 PM, "jenkins@cloudstack.org" <jenkins@cloudstack.org>
wrote:

>See <http://jenkins.buildacloud.org/job/simulator-singlerun/485/changes>
>
>Changes:
>
>[Rohit Yadav] CLOUDSTACK-7664: [UI] Handle change in API response for
>listloadbalancer
>
>------------------------------------------
>[...truncated 8938 lines...]
>[INFO] Final Memory: 44M/192M
>[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.5.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/../ut
>ils/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/../ut
>ils/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/targe
>t/db/create-schema-simulator.sql>
>========> Processing SQL file at
><http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/targe
>t/db/templates.simulator.sql>
>========> Processing SQL file at
><http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/targe
>t/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.x
>ml> to 
>/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.
>0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom
>[INFO] 
>------------------------------------------------------------------------
>[INFO] BUILD SUCCESS
>[INFO] 
>------------------------------------------------------------------------
>[INFO] Total time: 39.554s
>[INFO] Finished at: Wed Oct 01 15:58:32 EDT 2014
>[INFO] Final Memory: 43M/171M
>[INFO] 
>------------------------------------------------------------------------
>[simulator-singlerun] $ /bin/bash -x /tmp/hudson2342136899674022504.sh
>+ jps -l
>+ grep -q Launcher
>+ echo ''
>+ rm -rf /tmp/MarvinLogs
>+ echo Check for initialization of the management server
>Check for initialization of the management server
>+ COUNTER=0
>+ SERVER_PID=308
>+ '[' 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
>+ break
>+ grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
>+ echo Started OK pid 308
>Started OK pid 308
>+ sleep 20
>+ export 
>PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tool
>s/marvin>
>+ 
>PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tool
>s/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/Crypt
>o/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__Oct_01_2014_16_01_22_9SM5XS. All logs
>will be available here ====
>
>==== Deploy DC Started ====
>
>=== Data Center Settings are dumped to
>/tmp//MarvinLogs//DeployDataCenter__Oct_01_2014_16_01_22_9SM5XS/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//Oct_01_2014_16_05_10_VQCF55. 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.5.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.551s
>[INFO] Finished at: Wed Oct 01 16:14:50 EDT 2014
>[INFO] Final Memory: 25M/121M
>[INFO] 
>------------------------------------------------------------------------
>+ sleep 10
>+ kill -KILL 308
>/tmp/hudson2342136899674022504.sh: line 44: kill: (308) - 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] - 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


Mime
View raw message