You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 7, 2026. It is now read-only.
All tests in ITDMLTest.java relies on the same INSERT_DML statement. Each test executes the INSERT_DML & DELETE_DML statements, except abortOnceShouldSucceedAfterRetry test. All tests executed after abortOnceShouldSucceedAfterRetry will fail with "Row already exists" error.
Short term fix:
add the DELETE_DML into the test too
Correct / Long term fix:
refactor the test cases to not rely on the same set of INSERT/DELETE_dml statements. These tests should be independent (dont try to create a database/create a new table for each test, that will make them slow). Let each test run its own unique INSERT DML that does not interfere with another tests execution.
All tests in ITDMLTest.java relies on the same INSERT_DML statement. Each test executes the INSERT_DML & DELETE_DML statements, except abortOnceShouldSucceedAfterRetry test. All tests executed after abortOnceShouldSucceedAfterRetry will fail with "Row already exists" error.
Short term fix:
Correct / Long term fix: