[ https://issues.apache.org/jira/browse/HADOOP-14946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490507#comment-16490507 ]
Steve Loughran commented on HADOOP-14946: ----------------------------------------- bq. Attempt at a joke / me grasping at an explanation for your last stack trace. No worries, didn't know NTP logged much. FWIW, if I'd been testing in a VM, you can get massive clock jumps, but its hard to defend against. bq. Aside: Ideally we'd have a Timer or Ticker "fake time source" we could inject into S3AFileSystem and DynamoDBMS it exists, just needs to be integrated, somehow org.apache.hadoop.util.FakeTimer > S3Guard testPruneCommandCLI can fail > ------------------------------------ > > Key: HADOOP-14946 > URL: https://issues.apache.org/jira/browse/HADOOP-14946 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.0.0 > Reporter: Steve Loughran > Assignee: Gabor Bota > Priority: Major > Attachments: HADOOP-14946.001.patch, HADOOP-14946.002.patch > > > The test of the S3Guard CLI prune can sometimes fail on parallel test runs. > Assumption: it is the parallelism which is causing the problem > {code} > org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB > testPruneCommandCLI(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB) > Time elapsed: 10.765 sec <<< FAILURE! > java.lang.AssertionError: Pruned children count [] expected:<1> but was:<0> > at org.junit.Assert.fail(Assert.java:88) > {code} -- 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