[
https://issues.apache.org/jira/browse/CLOUDSTACK-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551878#comment-14551878
]
ASF GitHub Bot commented on CLOUDSTACK-8394:
--------------------------------------------
GitHub user gauravaradhye opened a pull request:
https://github.com/apache/cloudstack/pull/267
CLOUDSTACK-8394: Skipping recurring snapshot test cases for Hyperv and LXC
Snapshot feature is not supported on Hyperv and LXC hypervisors. Skipping
related test cases.
Log:
Test Recurring Snapshot data Disk ... SKIP: Snapshots feature is not
supported on Hyper-V/LXC
Test Recurring Snapshot Root Disk ... SKIP: Snapshots feature is not
supported on Hyper-V/LXC
----------------------------------------------------------------------
Ran 2 tests in 0.002s
OK (SKIP=2)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gauravaradhye/cloudstack 8394
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/267.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #267
----
commit b192c5fd27ed151f46dcea6e776c8133940757cb
Author: Gaurav Aradhye <[email protected]>
Date: 2015-05-20T06:02:16Z
CLOUDSTACK-8394: Skipping recurring snapshot test cases for Hyperv and LXC
----
> Skip test cases through setUp() instead of setUpClass()
> -------------------------------------------------------
>
> Key: CLOUDSTACK-8394
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8394
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Affects Versions: Future
> Reporter: Gaurav Aradhye
> Assignee: Gaurav Aradhye
> Labels: automation
> Fix For: Future
>
>
> When the tests are skipped through setUpClass, the statement "raise
> unittest.SkipTest()" is used. This is seen as exception in the logs. To avoid
> this, alternatively we can set class level variable in setUpClass and read
> this variable value in setUp() and skip the test case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
