>        } catch (IOException e) {
>           Assert.fail();
> +      } finally {
> +         // TODO: remove swallowIOException over-optimization and just use 
> Closeables2.closeQuietly

Yes, curious what this was for. This is in a *live test*, after all - not sure 
what the benefit here is of providing this option?

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

Reply via email to