[jira] [Commented] (HADOOP-13183) S3A proxy tests fail after httpclient/httpcore upgrade.
[ https://issues.apache.org/jira/browse/HADOOP-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292772#comment-15292772 ] Hudson commented on HADOOP-13183: - SUCCESS: Integrated in Hadoop-trunk-Commit #9830 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9830/]) HADOOP-13183. S3A proxy tests fail after httpclient/httpcore upgrade. (cnauroth: rev 93258459faf56bc84121ba99d20eaef95273329e) * hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/TestS3AConfiguration.java > S3A proxy tests fail after httpclient/httpcore upgrade. > --- > > Key: HADOOP-13183 > URL: https://issues.apache.org/jira/browse/HADOOP-13183 > Project: Hadoop Common > Issue Type: Bug > Components: fs/s3 >Reporter: Chris Nauroth >Assignee: Steve Loughran > Fix For: 2.8.0 > > Attachments: HADOOP-13183-branch-2-001.patch > > > HADOOP-12767 upgraded the httpclient and httpcore dependency versions. After > that, I started seeing failures in S3A tests related to proxy handling. If I > revert that patch locally, the tests pass again. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13183) S3A proxy tests fail after httpclient/httpcore upgrade.
[
https://issues.apache.org/jira/browse/HADOOP-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291896#comment-15291896
]
Hadoop QA commented on HADOOP-13183:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 11s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
25s {color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 12s
{color} | {color:green} branch-2 passed with JDK v1.8.0_91 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 13s
{color} | {color:green} branch-2 passed with JDK v1.7.0_101 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
13s {color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 18s
{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
29s {color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 12s
{color} | {color:green} branch-2 passed with JDK v1.8.0_91 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 14s
{color} | {color:green} branch-2 passed with JDK v1.7.0_101 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
13s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 9s
{color} | {color:green} the patch passed with JDK v1.8.0_91 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 9s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 11s
{color} | {color:green} the patch passed with JDK v1.7.0_101 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 11s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
11s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 15s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
10s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
39s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 9s
{color} | {color:green} the patch passed with JDK v1.8.0_91 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 12s
{color} | {color:green} the patch passed with JDK v1.7.0_101 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 10s
{color} | {color:green} hadoop-aws in the patch passed with JDK v1.8.0_91.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 10s
{color} | {color:green} hadoop-aws in the patch passed with JDK v1.7.0_101.
{color} |
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m 17s
{color} | {color:red} The patch generated 1 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 12m 27s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:babe025 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12804996/HADOOP-13183-branch-2-001.patch
|
| JIRA Issue | HADOOP-13183 |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux ec693a0f0ccf 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | branch-2 / f7ffa1a |
| Default Java | 1.7.0_101 |
| Multi-JDK versions |
[jira] [Commented] (HADOOP-13183) S3A proxy tests fail after httpclient/httpcore upgrade.
[ https://issues.apache.org/jira/browse/HADOOP-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291673#comment-15291673 ] Steve Loughran commented on HADOOP-13183: - Chris: I can replicate this on a linux Java 8 JVM; I'm not seeing it in the IOE exception branch, so think maybe I've somehow addressed it there...and perhaps why I didn't catch this earlier. What's probably happening is httpclient is returning a different error string; the two proxy tests are looking for specific text/numbers in them. Fix? I think we should just downgrade to catching the exception and not look at the text inside. > S3A proxy tests fail after httpclient/httpcore upgrade. > --- > > Key: HADOOP-13183 > URL: https://issues.apache.org/jira/browse/HADOOP-13183 > Project: Hadoop Common > Issue Type: Bug > Components: fs/s3 >Reporter: Chris Nauroth >Assignee: Steve Loughran > > HADOOP-12767 upgraded the httpclient and httpcore dependency versions. After > that, I started seeing failures in S3A tests related to proxy handling. If I > revert that patch locally, the tests pass again. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13183) S3A proxy tests fail after httpclient/httpcore upgrade.
[ https://issues.apache.org/jira/browse/HADOOP-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291616#comment-15291616 ] Chris Nauroth commented on HADOOP-13183: I see the problem on both trunk (Java 8) and branch-2.8 (Java 7). > S3A proxy tests fail after httpclient/httpcore upgrade. > --- > > Key: HADOOP-13183 > URL: https://issues.apache.org/jira/browse/HADOOP-13183 > Project: Hadoop Common > Issue Type: Bug > Components: fs/s3 >Reporter: Chris Nauroth >Assignee: Steve Loughran > > HADOOP-12767 upgraded the httpclient and httpcore dependency versions. After > that, I started seeing failures in S3A tests related to proxy handling. If I > revert that patch locally, the tests pass again. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13183) S3A proxy tests fail after httpclient/httpcore upgrade.
[
https://issues.apache.org/jira/browse/HADOOP-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291577#comment-15291577
]
Chris Nauroth commented on HADOOP-13183:
If I {{git checkout 22ff9e68d1d9f27d62455c15fb1242538551aca9}} (which is the
HADOOP-12767 commit), then I see failures in the {{TestS3AConfiguration}} proxy
tests. If I go one commit back by running {{git checkout
22ff9e68d1d9f27d62455c15fb1242538551aca9^}}, then the tests pass again. See
below for stack traces.
{code}
Running org.apache.hadoop.fs.s3a.TestS3AConfiguration
Tests run: 14, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 4.814 sec <<<
FAILURE! - in org.apache.hadoop.fs.s3a.TestS3AConfiguration
testProxyConnection(org.apache.hadoop.fs.s3a.TestS3AConfiguration) Time
elapsed: 2.007 sec <<< ERROR!
com.amazonaws.AmazonClientException: Unable to execute HTTP request: Connection
refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:120)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
at
org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:328)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
at
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at
com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:728)
at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
at
com.amazonaws.services.s3.AmazonS3Client.headBucket(AmazonS3Client.java:1107)
at
com.amazonaws.services.s3.AmazonS3Client.doesBucketExist(AmazonS3Client.java:1070)
at
org.apache.hadoop.fs.s3a.S3AFileSystem.initialize(S3AFileSystem.java:208)
at
org.apache.hadoop.fs.s3a.S3ATestUtils.createTestFileSystem(S3ATestUtils.java:52)
at
org.apache.hadoop.fs.s3a.TestS3AConfiguration.testProxyConnection(TestS3AConfiguration.java:123)
testAutomaticProxyPortSelection(org.apache.hadoop.fs.s3a.TestS3AConfiguration)
Time elapsed: 0.936 sec <<< ERROR!
com.amazonaws.AmazonClientException: Unable to execute HTTP request: Connection
refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:120)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
at
org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:328)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
at
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at
com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:728)
at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
at
