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

Mark Gui edited comment on HDDS-5139 at 5/6/21, 3:57 AM:
---------------------------------------------------------

As Marton pointed out, we should wait for the merge master pr 
[https://github.com/apache/ozone/pull/2180,] and fix this.


was (Author: markgui):
As Marton pointed out, I should wait for the merge master pr 
[https://github.com/apache/ozone/pull/2180,] and fix this.

> Restructure the acceptance test groups (unsecure/secure/misc)
> -------------------------------------------------------------
>
>                 Key: HDDS-5139
>                 URL: https://issues.apache.org/jira/browse/HDDS-5139
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Marton Elek
>            Assignee: Mark Gui
>            Priority: Blocker
>
> Ozone executes the acceptance test parallel. 
> On master we execute secure (1h38m) unsecure (42m) and misc (1h6m).
> Upgrade branch has secure (2h6m) unsecure (42m) and acceptance (1h13m)
> While some increase in the build time is necessary to run upgrade/downgrade 
> scenario we can adjust the parallel execution and instead of increasing the 
> build time of the slowest (secure) job we can add the new tests to the 
> fastest (unsecure) job.
> While we would use the same build resources, the overall time of build can be 
> significant faster (less time to wait until the build is finished)
> This task is as easy as adding "#suite:unsecure" tags to the right test.sh 
> scripts (I guess to the compose/upgrade/test.sh)
> Please note that HDDS-5125 is just merged to the master, so we need to merge 
> master back to the branch to get the up-to-date numbers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to