cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Santhosh Edukulla <santhosh.eduku...@citrix.com>
Subject RE: Integration Tests on TravisCI
Date Thu, 14 Aug 2014 15:23:21 GMT
Few test suites under smoke/misc folder say test_vm_ha,test_vm_sync, test_deploy_vm have a
dependency to run only on simulator and sequentially with no entries available in CS, these
are written using simulator mocks, so if you run along with other test suites they will fail.

with -w switch, nose will run all along with other suites under smoke, so, you can use noseexclude
plugin and exclude them from normal run, and later run them in serially with out any dependencies.
To exclude add the switch --exclude-dir="../smoke/misc" to nose command. 

Other should work. Where can we see the detailed logs for these runs?

Regards,
Santhosh
________________________________________
From: Ian Duffy [ian@ianduffy.ie]
Sent: Thursday, August 14, 2014 9:42 AM
To: CloudStack Dev
Subject: Integration Tests on TravisCI

Hi All,

TL;DR: See https://github.com/imduffy15/Cloudstack-Clone specifically
.travis.yml and tools/travis/*

Myself, Sebastien and Rohit have been looking at executing Cloudstack's
integration tests against the simulator using http://travis-ci.org.

Doing this will enable us to execute the integration tests on all branches
for free. It also means all community forks could make use of the travis-ci
service too.


Currently all tests are executing, there appears to be some tests failing
on the simulator specifically:

test_routers test_secondary_storage test_service_offerings test_ssvm
test_templates test_vm_ha test_vm_life_cycle test_vm_sync test_volumes
test_vpc_vpn

Running these tests both locally and on travis-ci on the 4.4 branch I'm
seeing failures. Anybody know why?

Full console output of test execution available at
https://travis-ci.org/imduffy15/Cloudstack-Clone/builds/32530691

For those interested in how all this is working:

I have a fork of the Cloudstack source on my github:
https://github.com/imduffy15/Cloudstack-Clone

In the root of this repository you will find a .travis.yml file. This file
executes a few different stages:

 before install: Installs all dependencies and build tools.
 install: compiles cloudstack
 before_script: starts up cloudstack and deploys the setup/dev/advanced.cfg
 script: executes the nosetests

One limitation with travis-ci is that a job is not allowed to run for
longer than 50mins.

In order to get around this 3 separate environments are provisioned. They
are described as below:

Environment 1 runs test_affinity_groups test_deploy_vm
test_deploy_vms_with_varied_deploymentplanners
  test_disk_offerings test_global_settings test_guest_vlan_range test_iso
test_multipleips_per_nic
  test_network test_non_contigiousvlan

Environment 2 runs: test_over_provisioning test_portable_publicip
test_primary_storage test_privategw_acl
  test_public_ip_range test_pvlan test_regions test_reset_vm_on_reboot
test_resource_detail"

Environment 3 runs: test_routers test_secondary_storage
test_service_offerings test_ssvm test_templates
  test_vm_ha test_vm_life_cycle test_vm_sync test_volumes test_vpc_vpn

Thanks!

Ian

Mime
View raw message