[IMPALA-12522] test_alter_table_recover could finish less than 10 seconds with JDK 17 when enable_async_ddl_execution is False

• Type: Test
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Labels: broken-build flaky-test
• Epic Color: ghx-label-1
• Assignee: Joe McDonnell
• Reporter: Fang-Yu Rao
• Created: 26/Oct/23 21:50
• Updated: 27/Oct/23 01:12

Description

We found that test_alter_table_recover() could finish the execution within 10 seconds with JDK 17 when enable_async_ddl_execution is False and thus the check in the else branch could fail. Don't know it has something to do with JDK but maybe we could reduce the expected execution time a little bit to make the test less flaky.

      # In sync mode:
      #  The entire DDL is processed in the exec step with delay. exec_time should be
      #  more than 10 seconds.
      #
      # In async mode:
      #  The compilation of DDL is processed in the exec step without delay. And the
      #  processing of the DDL plan is in wait step with delay. The wait time should
      #  definitely take more time than 10 seconds.
      if enable_async_ddl:
        assert(wait_time >= 10)
      else:
        assert(exec_time >= 10)