[ 
https://issues.apache.org/jira/browse/HIVE-26332?focusedWorklogId=801645&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-801645
 ]

ASF GitHub Bot logged work on HIVE-26332:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Aug/22 10:00
            Start Date: 18/Aug/22 10:00
    Worklog Time Spent: 10m 
      Work Description: ayushtkn commented on PR #3375:
URL: https://github.com/apache/hive/pull/3375#issuecomment-1219294963

   I too need this, Was going to create a Jira and bumped into this. Actually 
when integrating Ozone with Hive, I observed without moving up the surefire 
plugin version to 3.0.0-M5, for some strange reasons the test weren't running. 
I didn't figure out the reason for that, but moving to 3.0.0-M5 sorted things 
for me.
   @zabetak Do you have any pointers like if there are any challenges moving up 
here?




Issue Time Tracking
-------------------

    Worklog Id:     (was: 801645)
    Time Spent: 40m  (was: 0.5h)

> Upgrade maven-surefire-plugin to 3.0.0-M7
> -----------------------------------------
>
>                 Key: HIVE-26332
>                 URL: https://issues.apache.org/jira/browse/HIVE-26332
>             Project: Hive
>          Issue Type: Task
>          Components: Testing Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently we use 3.0.0-M4 which was released in 2019. Since there have been 
> multiple bug fixes and improvements:
> [https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20(fixVersion%20%3D%203.0.0-M5%20OR%20fixVersion%20%3D%203.0.0-M6%20OR%20fixVersion%20%3D%203.0.0-M7)%20ORDER%20BY%20resolutiondate%20%20DESC%2C%20key]
> Worth mentioning that interaction with JUnit5 is much more mature as well and 
> this is one of the main reasons driving this upgrade.
>  



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

Reply via email to