I added some logging to try to get more information about the flaky test.
My current expectation is that it's related to the common tables that are reused across multiple tests. If the test framework can run multiple tests in parallel, these tests can interfere in moments of commiting transactions.
The particular test mentioned in the issue fails at the moment of commit() call. Internally, it tries to make batchInsert() and fails with the ArrayIndexOutOfBoundsException exception (exception itself raised inside the oracle driver)
I added some logging to try to get more information about the flaky test.
My current expectation is that it's related to the common tables that are reused across multiple tests. If the test framework can run multiple tests in parallel, these tests can interfere in moments of commiting transactions.
The particular test mentioned in the issue fails at the moment of
commit()call. Internally, it tries to makebatchInsert()and fails with the ArrayIndexOutOfBoundsException exception (exception itself raised inside the oracle driver)