[ https://issues.apache.org/jira/browse/HADOOP-18697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714959#comment-17714959 ]
Ayush Saxena commented on HADOOP-18697: --------------------------------------- Just passing by, the exception changed btw. In the description {noformat} Gauge named stream_read_blocks_in_cache with expected value 3] expected:<[3]L> but was:<[2]L>{noformat} And the new one {noformat} Gauge named stream_read_blocks_in_cache with expected value 0] expected:<[0]L> but was:<[1]L>{noformat} Both are different assertions, one before close and one after > transient failure of ITestS3APrefetchingInputStream.testRandomReadLargeFile > --------------------------------------------------------------------------- > > Key: HADOOP-18697 > URL: https://issues.apache.org/jira/browse/HADOOP-18697 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3, test > Affects Versions: 3.4.0 > Reporter: Steve Loughran > Priority: Major > > intermittent failure of test; caller in uk, no VPN involved. does not always > surface > {code} > testRandomReadLargeFile(org.apache.hadoop.fs.s3a.ITestS3APrefetchingInputStream) > Time elapsed: 19.913 s <<< FAILURE! > org.junit.ComparisonFailure: [Gauge named stream_read_blocks_in_cache with > expected value 3] expected:<[3]L> but was:<[2]L> > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org