monthonk opened a new pull request, #4006:
URL: https://github.com/apache/hadoop/pull/4006

   ### Description of PR
   
   There's no tests of hadoop -fs commands against S3a. With some tests we can 
see problems when using these commands with S3a (HADOOP-13294).
   
   From the command list in 
[FileSystemShell](https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/FileSystemShell.html),
 I added tests for each of them, verify expected output from stdout, stderr and 
return code. Some tests might be a bit long because I'm trying to group the 
commands and run them together so it won't take too long.
   
   ### Changes
   - Adding hadoop -fs commands test for S3a
   
   ### How was this patch tested?
   
   Tested in ` eu-west-1` with `mvn -Dparallel-tests -DtestsThreadCount=16 
clean verify`
   
   ```
   [INFO] Results:
   [INFO] 
   [WARNING] Tests run: 1070, Failures: 0, Errors: 0, Skipped: 185
   [INFO] Results:
   [INFO] 
   [WARNING] Tests run: 108, Failures: 0, Errors: 0, Skipped: 68
   ```
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [x] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [x] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to