Yeah, those ghost failures hit me too - not sure where they came from. But hey.
Lemme know when this gets to 1.9.x so I can pull it into our internal app. =)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#issuecomment-110168828
Closed #141.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#event-325309671
Pushed to master as
[a3cb4490](http://git-wip-us.apache.org/repos/asf/jclouds-labs-google/commit/a3cb4490).
I'll push it to 1.9.x later today as the merge there presented a couple
conflicts.
---
Reply to this email directly or view it on GitHub:
yy - passes with that changed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#issuecomment-109359455
Ok, https://cloud.google.com/compute/docs/instances/#stop_job seems to explain
it - TERMINATED is actually stopped here.
I started coding this up and ran into the same problem. I'll look into it.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#issuecomment-106641024
rebuild please
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#issuecomment-106210151
Looks like an internal Jenkins failure, rebuild please
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/141#issuecomment-106219464
