You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2012/10/25 00:56:13 UTC

[jira] [Created] (HADOOP-8979) TestHttpServer fails on Windows

Chris Nauroth created HADOOP-8979:
-------------------------------------

             Summary: TestHttpServer fails on Windows
                 Key: HADOOP-8979
                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
             Project: Hadoop Common
          Issue Type: Bug
          Components: net
    Affects Versions: trunk-win
            Reporter: Chris Nauroth
            Assignee: Chris Nauroth


The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.


--
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

[jira] [Updated] (HADOOP-8979) TestHttpServer fails on Windows

Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Srinivas updated HADOOP-8979:
------------------------------------

       Resolution: Fixed
    Fix Version/s: trunk-win
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Chris, thank you for fixing the test failure. +1 for the patch.

I committed it to branch-trunk-win.
                
> TestHttpServer fails on Windows
> -------------------------------
>
>                 Key: HADOOP-8979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: 3.0.0, trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: trunk-win
>
>         Attachments: HADOOP-8979.patch
>
>
> The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.

--
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

[jira] [Commented] (HADOOP-8979) TestHttpServer fails on Windows

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488706#comment-13488706 ] 

Hadoop QA commented on HADOOP-8979:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12551682/HADOOP-8979.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-common-project/hadoop-common.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1693//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1693//console

This message is automatically generated.
                
> TestHttpServer fails on Windows
> -------------------------------
>
>                 Key: HADOOP-8979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: 3.0.0, trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-8979.patch
>
>
> The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.

--
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

[jira] [Commented] (HADOOP-8979) TestHttpServer fails on Windows

Posted by "Chris Nauroth (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483697#comment-13483697 ] 

Chris Nauroth commented on HADOOP-8979:
---------------------------------------

{code}
Running org.apache.hadoop.http.TestHttpServer
Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 14.497 sec <<< FAILURE!
testBindAddress(org.apache.hadoop.http.TestHttpServer)  Time elapsed: 531 sec  <<< FAILURE!
java.lang.AssertionError: 
	at org.junit.Assert.fail(Assert.java:91)
	at org.junit.Assert.assertTrue(Assert.java:43)
	at org.junit.Assert.assertTrue(Assert.java:54)
	at org.apache.hadoop.http.TestHttpServer.checkBindAddress(TestHttpServer.java:531)
	at org.apache.hadoop.http.TestHttpServer.testBindAddress(TestHttpServer.java:500)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
	at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
{code}

                
> TestHttpServer fails on Windows
> -------------------------------
>
>                 Key: HADOOP-8979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>
> The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.

--
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

[jira] [Updated] (HADOOP-8979) TestHttpServer fails on Windows

Posted by "Chris Nauroth (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated HADOOP-8979:
----------------------------------

    Status: Patch Available  (was: Open)
    
> TestHttpServer fails on Windows
> -------------------------------
>
>                 Key: HADOOP-8979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: 3.0.0, trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-8979.patch
>
>
> The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.

--
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

[jira] [Commented] (HADOOP-8979) TestHttpServer fails on Windows

Posted by "Chuan Liu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489084#comment-13489084 ] 

Chuan Liu commented on HADOOP-8979:
-----------------------------------

+1 Nice discovery and fix!
                
> TestHttpServer fails on Windows
> -------------------------------
>
>                 Key: HADOOP-8979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: 3.0.0, trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-8979.patch
>
>
> The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.

--
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

[jira] [Updated] (HADOOP-8979) TestHttpServer fails on Windows

Posted by "Chris Nauroth (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated HADOOP-8979:
----------------------------------

     Target Version/s: 3.0.0, trunk-win  (was: trunk-win)
    Affects Version/s: 3.0.0
    
> TestHttpServer fails on Windows
> -------------------------------
>
>                 Key: HADOOP-8979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: 3.0.0, trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>
> The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.

--
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

[jira] [Updated] (HADOOP-8979) TestHttpServer fails on Windows

Posted by "Chris Nauroth (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated HADOOP-8979:
----------------------------------

    Attachment: HADOOP-8979.patch

This had been fixed in branch-1-win, but it wasn't included in the merge to branch-trunk-win.  The attached patch fixes it.  We can start this patch in trunk and then merge to branch-trunk-win.

Jenkins will give a -1 for no new tests.  This condition is already covered sufficiently by TestHttpServer.testBindAddress, which had been failing on Windows prior to this patch.
                
> TestHttpServer fails on Windows
> -------------------------------
>
>                 Key: HADOOP-8979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8979
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: net
>    Affects Versions: 3.0.0, trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-8979.patch
>
>
> The test asserts status of binding an HTTP server to a port.  Perhaps there is some platform-specific difference in handling this on Windows.

--
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