You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Raymond Xu (Jira)" <ji...@apache.org> on 2022/04/28 12:43:00 UTC

[jira] [Updated] (HUDI-3023) Fix order of tests

     [ https://issues.apache.org/jira/browse/HUDI-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raymond Xu updated HUDI-3023:
-----------------------------
    Epic Link: HUDI-3303  (was: HUDI-1248)

> Fix order of tests
> ------------------
>
>                 Key: HUDI-3023
>                 URL: https://issues.apache.org/jira/browse/HUDI-3023
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: Sagar Sumit
>            Assignee: Sagar Sumit
>            Priority: Major
>
> Recently, we encountered an issue in integ tests where namenode was not ready yet to receive connections (still in safemode) and hdfs commands in ITTestHoodieDemo setup were not succeeeding. The namenode typically takes some time (2-3 minutes) to come up. While adding a delay is a workaround, it would be better to execute this test after others like ITTestHoodieSyncCommand and ITTestHoodieSanity. With JUnit 5.8 we can order test classes and as we already have a working patch for upgrading junit (https://github.com/apache/hudi/pull/3748) we should consider ficing the order to avoid flakiness.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)