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

Attila Doroszlai commented on HDDS-5093:
----------------------------------------

bq. I checked it again, and one it's not just about the matrix build: new 
docker compose start/stop commands are added.
bq. I would consider creating a new compose folder (ozonefs) where we test the 
ozone with file system enabled features.

It was originally added in separate compose folder.  I have asked for adding it 
to the {{ozone}} test to avoid duplication only for the sake of 1-2 changed 
config properties.  See 
https://github.com/apache/ozone/pull/2071#issuecomment-804780817 and later 
comments.

I don't think separate compose folder would reduce run time, cluster still has 
to be started.

> [FSO] Reducing time of ozonefs acceptance testmatrix
> ----------------------------------------------------
>
>                 Key: HDDS-5093
>                 URL: https://issues.apache.org/jira/browse/HDDS-5093
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Marton Elek
>            Assignee: Marton Elek
>            Priority: Major
>
> Today we execute ozonefs/ozonefs.robot with compose/ozone/test.sh with 
> multiple matrix parameters:
> {code}
> for scheme in ofs o3fs; do
>     for bucket in link bucket; do
>        #test ozonefs/ozonefs.robot
>    done
> done
> {code}
> HDDS-2939 doubles these 4 executions with introducing the layout parameter 
> (simple vs prefix).  At the same time the execution time of acceptance 
> (unsecure) tests are increased from 37 minutes to 57 minutes.
> I would suggest suggesting to use only selected tests from this 2 x 2 x 2 
> matrix.
> For example:
> bucket / o3fs / prefix
> link / ofs / simple
> bucket / ofs / prefix
>  



--
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