[HADOOP-16057] IndexOutOfBoundsException in ITestS3GuardToolLocal

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Component/s: fs/s3, test
• Target Version/s: 3.3.0
• Assignee: Adam Antal
• Reporter: Steve Loughran
• Created: 18/Jan/19 18:03
• Updated: 19/Feb/19 12:42
• Resolved: 19/Feb/19 12:42

Description

A new test from HADOOP-15843 is failing: testDestroyNoArgs; one arg too short in the command line.

Test run with {{ -Ds3guard -Ddynamodb}}

[ERROR] testDestroyNoArgs(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolLocal)  Time elapsed: 0.761 s  <<< ERROR!
java.lang.IndexOutOfBoundsException: toIndex = 1
	at java.util.ArrayList.subListRangeCheck(ArrayList.java:1004)
	at java.util.ArrayList.subList(ArrayList.java:996)
	at org.apache.hadoop.fs.shell.CommandFormat.parse(CommandFormat.java:89)
	at org.apache.hadoop.fs.s3a.s3guard.S3GuardTool.parseArgs(S3GuardTool.java:371)
	at org.apache.hadoop.fs.s3a.s3guard.S3GuardTool$Destroy.run(S3GuardTool.java:626)
	at org.apache.hadoop.fs.s3a.s3guard.S3GuardTool.run(S3GuardTool.java:399)
	at org.apache.hadoop.fs.s3a.s3guard.AbstractS3GuardToolTestBase.lambda$testDestroyNoArgs$4(AbstractS3GuardToolTestBase.java:403)

Issue Links

• is broken by: HADOOP-15843 s3guard bucket-info command to not print a stack trace on bucket-not-found