The AbortedTransactionTest relies on the behaviour fixed in duckdb/duckdb#20119, which caused the transaction COMMIT to throw an error, and I don't know of another way to make the transaction COMMIT throw an error. That PR I believe is scheduled for release with 1.5, so when updating to 1.5 the test might start failing and it may be best to just delete it or skip it.
The AbortedTransactionTest relies on the behaviour fixed in duckdb/duckdb#20119, which caused the transaction
COMMITto throw an error, and I don't know of another way to make the transactionCOMMITthrow an error. That PR I believe is scheduled for release with 1.5, so when updating to 1.5 the test might start failing and it may be best to just delete it or skip it.