cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-521) Build will hung up when doing test for TestAgentShell
Date Sat, 23 Mar 2013 18:15:15 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prasanna Santhanam reassigned CLOUDSTACK-521:
---------------------------------------------

    Assignee: gavin lee

Is this still an issue? I think tests that did db access and wgets are now removed from mvn
test.
                
> Build will hung up when doing test for TestAgentShell
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-521
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-521
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.1.0
>         Environment: CentOS 6.3 x86_64
>            Reporter: gavin lee
>            Assignee: gavin lee
>              Labels: TestAgentShell, build-failure
>             Fix For: 4.1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> 1> mvn build -Dnonoss
> 2> Build hung up at TESTING TestAgentShell
> 3> Following wget testing will cause hang up in TestAgentShell:
> AgentShell.wget("http://www.google.com/", file);
> Root Cause Analysis:
> In China mainland, Tested "wget http://www.google.com/" directly will find out the site
redirect to http://www.google.com.hk/, the index.html can be downloaded but the wget won't
exit since the length is unspecified.
> See below full dump:
> [root@ms-centos ~]# wget http://www.google.com/
> --2012-11-20 18:00:52--  http://www.google.com/
> Resolving www.google.com... 74.125.128.99, 74.125.128.106, 74.125.128.105, ...
> Connecting to www.google.com|74.125.128.99|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1353377006001067&usg=AFQjCNGols_39b19hsoCeTRDfImJLtmRkQ
[following]
> --2012-11-20 18:00:52--  http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1353377006001067&usg=AFQjCNGols_39b19hsoCeTRDfImJLtmRkQ
> Resolving www.google.com.hk... 74.125.128.199, 2404:6800:4005:c00::c7
> Connecting to www.google.com.hk|74.125.128.199|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://www.google.com.hk/ [following]
> --2012-11-20 18:00:52--  http://www.google.com.hk/
> Reusing existing connection to www.google.com.hk:80.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: “index.html
> [                                                             <=>      ] 3,877
      --.-K/s        
> 2012-11-20 18:15:52 (4.31 B/s) - Read error at byte 3877 (Connection timed out).Retrying.
> --2012-11-20 18:15:53--  (try: 2)  http://www.google.com.hk/
> Connecting to www.google.com.hk|74.125.128.199|:80... connected.
> HTTP request sent, awaiting response... 200 OK
>     The file is already fully retrieved; nothing to do.
> Since it will block build process, the test site should be changed to others, but which
one is good enough?
> I've tested http://www.baidu.com for both wget and TestAgentShell, both are ok.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message