[Bug]: Flaky test for TestInternalIcebergCatalogService$TableTests.testTableTransaction:

[klion26]

What happened?

2025-01-21T03:52:19.1457107Z [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 s - in org.apache.amoro.server.TestAmoroManagementConfValidator
2025-01-21T03:52:19.1474971Z 03:52:19.146 INFO org.apache.amoro.hive.HMSMockServer: -------------------------------------------------------------------------
2025-01-21T03:52:19.1475374Z 03:52:19.146 INFO org.apache.amoro.hive.HMSMockServer:     Shutdown HiveMetastoreServer 
2025-01-21T03:52:19.1475859Z 03:52:19.146 INFO org.apache.amoro.hive.HMSMockServer: -------------------------------------------------------------------------
2025-01-21T03:52:19.1476185Z 03:52:19.147 INFO org.apache.amoro.TestAms: Stop singleton mock AMS after testing.
2025-01-21T03:52:19.7173993Z [INFO] 
2025-01-21T03:52:19.7174361Z [INFO] Results:
2025-01-21T03:52:19.7174709Z [INFO] 
2025-01-21T03:52:19.7175003Z [ERROR] Errors: 
2025-01-21T03:52:19.7176611Z [ERROR]   TestInternalIcebergCatalogService$TableTests.testTableTransaction:174 » ServiceFailure Server error: PersistenceException: org.apache.ibatis.exceptions.PersistenceException: 
2025-01-21T03:52:19.7179631Z ### Error updating database.  Cause: org.apache.derby.shared.common.error.DerbySQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'TABLE_RUNTIME_PK' defined on 'TABLE_RUNTIME'.
2025-01-21T03:52:19.7182079Z ### The error may exist in org/apache/amoro/server/persistence/mapper/TableMetaMapper.java (best guess)
2025-01-21T03:52:19.7183185Z ### The error may involve org.apache.amoro.server.persistence.mapper.TableMetaMapper.insertTableRuntime-Inline
2025-01-21T03:52:19.7184066Z ### The error occurred while setting parameters
2025-01-21T03:52:19.7186560Z ### SQL: INSERT INTO table_runtime (table_id, catalog_name, db_name, table_name, current_snapshot_id, current_change_snapshotId, last_optimized_snapshotId, last_optimized_change_snapshotId, last_major_optimizing_time, last_minor_optimizing_time, last_full_optimizing_time, optimizing_status_code, optimizing_status_start_time, optimizing_process_id, optimizer_group, table_config, pending_input, table_summary) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
2025-01-21T03:52:19.7190801Z ### Cause: org.apache.derby.shared.common.error.DerbySQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'TABLE_RUNTIME_PK' defined on 'TABLE_RUNTIME'.
2025-01-21T03:52:19.7192807Z [INFO] 
2025-01-21T03:52:19.7193215Z [ERROR] Tests run: 605, Failures: 0, Errors: 1, Skipped: 8

please ref to the ci for more detail

Affects Versions

master

What table formats are you seeing the problem on?

No response

What engines are you seeing the problem on?

No response

How to reproduce

No response

Relevant log output

Anything else

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[klion26]

@Jzjsnow, please take a look at this. It seems to relate to the problem we encountered in production.