You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/11/03 16:30:25 UTC
[jira] Updated: (WHIRR-123) Cassandra integration tests hang if
whirr's scripts bucket is missing
[ https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated WHIRR-123:
-------------------------------
ps. the test doesn't cleanup properly in this case (ctrl-c after the hang) so be sure to check your ec2 instances and terminate any zombies assoc with the test.
> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
> Key: WHIRR-123
> URL: https://issues.apache.org/jira/browse/WHIRR-123
> Project: Whirr
> Issue Type: Bug
> Components: core, service/cassandra
> Affects Versions: 0.2.0
> Reporter: Patrick Hunt
> Priority: Critical
> Fix For: 0.3.0
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. The tests failed while verifying cassandra. Looking on the ec2 host I see the following in the stderr (nothing in stdout). Note - I had not created the 0.2.0-incubating bucket on s3, so while this test would never pass, it seems unusual that the test hangs forever rather than tear down the test and report an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.