[ 
https://issues.apache.org/jira/browse/YARN-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582220#comment-17582220
 ] 

ASF GitHub Bot commented on YARN-11257:
---------------------------------------

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

   ### Description of PR
   
   Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to some 
unit test failure
   
   JIRA - YARN-11257
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] 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?
   
   




> Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to some 
> unit test failure
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-11257
>                 URL: https://issues.apache.org/jira/browse/YARN-11257
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: groot
>            Assignee: groot
>            Priority: Major
>
> We need add Junit 5 dependency in
> {code:java}
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
> as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and 
> we have already updated TimelineStoreTestUtils from Junit 4 to 5.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to