Live tests for the subscription calculator have been fixed, so for me it is
good to merge (I'll do later today).
@Kentzo, @shevchenator, There is still a live test failing (not related to this
PR, and not a merge stopper, though):
Failed tests:
testEditTag(org.jclouds.cloudsigma2.CloudSigma2LasVegasLiveTest): expected [0]
but found [1]
Tests run: 50, Failures: 1, Errors: 0, Skipped: 1
testEditTag(org.jclouds.cloudsigma2.CloudSigma2LasVegasLiveTest) Time
elapsed: 0.698 sec <<< FAILURE!
java.lang.AssertionError: expected [0] but found [1]
at org.testng.Assert.fail(Assert.java:94)
at org.testng.Assert.failNotEquals(Assert.java:494)
at org.testng.Assert.assertEquals(Assert.java:123)
at org.testng.Assert.assertEquals(Assert.java:370)
at org.testng.Assert.assertEquals(Assert.java:380)
at
org.jclouds.cloudsigma2.CloudSigma2ApiLiveTest.checkTag(CloudSigma2ApiLiveTest.java:692)
at
org.jclouds.cloudsigma2.CloudSigma2ApiLiveTest.testEditTag(CloudSigma2ApiLiveTest.java:530)
It was already failing before:
>It fails in [this
>line](https://github.com/jclouds/jclouds-labs/blob/master/cloudsigma2/src/test/java/org/jclouds/cloudsigma2/CloudSigma2ApiLiveTest.java#L663).
> Is it possible that the tag edition does not properly handle the resource
>modification? Or is it something to fix in the live test itself?
Do you have any clue if it is something wrong in the test itself, or in the
API/backend?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/41#issuecomment-30113956
