jclouds-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sunny Gleason <notificati...@github.com>
Subject Re: [jclouds] Jclouds 136 -- Implementation of DynECT HTTP Redirect service API (#37)
Date Sat, 29 Jun 2013 16:55:58 GMT
> +      if (zone == null) {
> +         Job job = api.getZoneApi().scheduleCreateWithContact(fqdn, contact);
> +         checkNotNull(job, "unable to create zone %s", fqdn);
> +         getAnonymousLogger().info("created zone: " + job);
> +         assertEquals(job.getStatus(), Status.SUCCESS);
> +         assertEquals(api.getJob(job.getId()), job);
> +         zone = api.getZoneApi().publish(fqdn);
> +         checkNotNull(zone, "unable to publish zone %s", fqdn);
> +         getAnonymousLogger().info("published zone: " + zone);
> +      }
> +      checkZone(zone);
> +   }
> +
> +   @Test(dependsOnMethods = "testCreatePublishZone")
> +   public void testCreateAndPublishHttpRedirect() throws Exception {
> +      Thread.sleep(3000); // FIXME - figure out delays

Ah yes, the API was unforgiving while testing and threw a lot of "job in progress" exceptions.
I was going to ask @adriancole or anyone else if they have any suggestions for making the
live tests more robust and avoiding those conflicts, or if they're inevitable with the current
version of the service...

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/37/files#r4952487

Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message