[ https://issues.apache.org/jira/browse/HADOOP-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613669#comment-16613669 ]
Steve Loughran commented on HADOOP-15754: ----------------------------------------- These tests don't like me Test looking @ s3 london, before the patch went in. {code} INFO] Running org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB [ERROR] Tests run: 11, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 203.32 s <<< FAILURE! - in org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB [ERROR] testDynamoTableTagging(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB) Time elapsed: 7.251 s <<< ERROR! org.apache.hadoop.util.ExitUtil$ExitException: No region found from -region flag, config, or S3 bucket at org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB.testDynamoTableTagging(ITestS3GuardToolDynamoDB.java:119) [ERROR] testSetCapacityFailFastIfNotGuarded(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB) Time elapsed: 1.571 s <<< ERROR! java.io.FileNotFoundException: DynamoDB table '397a44b6-07fa-4d8e-b1ae-4546fa935e08' does not exist in region eu-west-1; auto-creation is turned off Caused by: com.amazonaws.services.dynamodbv2.model.ResourceNotFoundException: Requested resource not found: Table: 397a44b6-07fa-4d8e-b1ae-4546fa935e08 not found (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ResourceNotFoundException; Request ID: 0TDDT2J413EGGANJ25UIPB3SV7VV4KQNSO5AEMVJF66Q9ASUAAJG) {code} And here, ireland as the destination {code} DynamoDB [ERROR] testDynamoTableTagging(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB) Time elapsed: 4.932 s <<< ERROR! org.apache.hadoop.util.ExitUtil$ExitException: No region found from -region flag, config, or S3 bucket at org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB.testDynamoTableTagging(ITestS3GuardToolDynamoDB.java:126) {code} > s3guard: testDynamoTableTagging should clear existing config > ------------------------------------------------------------ > > Key: HADOOP-15754 > URL: https://issues.apache.org/jira/browse/HADOOP-15754 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.2.0 > Reporter: Aaron Fabbri > Assignee: Gabor Bota > Priority: Minor > Attachments: HADOOP-15754.001.patch > > > I recently committed HADOOP-14734 which adds support for tagging Dynamo DB > tables for S3Guard when they are created. > > Later, when testing another patch, I hit a test failure because I still had a > tag option set in my test configuration (auth-keys.xml) that was adding my > own table tag. > {noformat} > [ERROR] > testDynamoTableTagging(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB) > Time elapsed: 13.384 s <<< FAILURE! > java.lang.AssertionError: expected:<2> but was:<3> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB.testDynamoTableTagging(ITestS3GuardToolDynamoDB.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at > org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74){noformat} > I think the solution is just to clear any tag.* options set in the > configuration at the beginning of the test. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org