[
https://issues.apache.org/jira/browse/HADOOP-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624629#comment-17624629
]
ASF GitHub Bot commented on HADOOP-18508:
-----------------------------------------
steveloughran opened a new pull request, #5081:
URL: https://github.com/apache/hadoop/pull/5081
* adds job id to fork id
* adds option to disable root tests
* documents this
* gets more tests working under the job/fork subdir rather than absolute
paths. tracking them down is tricky.
### How was this patch tested?
running the forked tests with different job ids, disabling root dir cleanup
and seeing what was created in separate subdirs
### 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?
- [ ] 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)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> support multiple s3a integration test runs on same bucket in parallel
> ---------------------------------------------------------------------
>
> Key: HADOOP-18508
> URL: https://issues.apache.org/jira/browse/HADOOP-18508
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.3.9
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> to have (internal, sorry) jenkins test runs work in parallel, they need to
> share the same bucket so
> # must have a prefix for job id which is passed in to the path used for forks
> # support disabling root tests so they don't stamp on each other
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
