Closed Tardo closed 5 months ago
Hi @frahikLV, @alexis-via, @moylop260, some modules you are maintaining are being modified, check this out!
Hi @Tardo
Thank you for your fix
Can I ask for more details about reproducing the error, please?
Hi @moylop260
I can reproduce it when testing: account_move_name_sequence, contract_payment_mode
contract_payment_mode fails with: psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update
@moylop260 One of the threads fails with: (could not obtain lock on row in relation "ir_sequence_date_range")
So, maybe server-ux/date_range is involved.
I can not reproduce it using the following command:
odoo-bin -i account_move_name_sequence,contract_payment_mode,date_range --test-enable
What command are you using to reproduce it?
Something like:
odoo-bin --test-enable --stop-after-init --workers=0 -i date_range,account_move_name_sequence,contract_payment_mode
I have many others OCA modules installed in the DB.
/ocabot merge patch
On my way to merge this fine PR! Prepared branch 15.0-ocabot-merge-pr-1858-by-moylop260-bump-patch, awaiting test results.
Congratulations, your PR was merged at 203f724bc6ae19511761d1e31835efe2cb1f6938. Thanks a lot for contributing to OCA. ❤️
Before this change, if one thread raises an exception, the other thread could continue working without waiting for it... which could cause problems with other tests.