runbot/forwardport/tests
Xavier Morel c4c32957be [FIX] runbot_merge: removal of fw tasks on limit update
There is no check or unique index, so nothing actually prevents having
multiple fw tasks for the same batch.

In that case, if we try to update the limit the handler will crash
because the code assumes a single forwardport task per batch.

Triggered by nle on odoo/odoo#201394 probably while trying to recover
from the incident of March 13/14 (which was not going to work as the
forwardport queue itself was hosed, see two commits above for the
reason).
2025-03-14 16:02:22 +01:00
..
conftest.py [REM] *: default_crons fixture 2024-08-02 15:14:50 +02:00
test_backport.py [ADD] *: PR backport wizard 2024-10-22 11:41:58 +02:00
test_batches.py [FIX] *: double forwardport when adding a PR to an existing batch 2025-02-11 14:27:53 +01:00
test_conflicts.py [IMP] *: cleanup status contexts in tests 2025-02-06 14:55:28 +01:00
test_limit.py [FIX] runbot_merge: removal of fw tasks on limit update 2025-03-14 16:02:22 +01:00
test_overrides.py [IMP] *: cleanup status contexts in tests 2025-02-06 14:55:28 +01:00
test_simple.py [IMP] *: add closed PR to the branch deleter 2025-03-11 15:28:28 +01:00
test_skipmerge.py [ADD] *: fw=skipmerge 2025-02-04 08:05:15 +01:00
test_updates.py [IMP] *: cleanup status contexts in tests 2025-02-06 14:55:28 +01:00
test_weird.py [ADD] forwardport: test on resuming fw by hand 2025-02-14 13:38:21 +01:00