runbot/forwardport
Xavier Morel 4b5dfc2005 [FIX] forwardport: broken fp if intermediate commit requires renamelimit=0
On a cherrypick failing due to renamelimit issues, the cherrypick
would be retried after resetting the target to its *original* commit.

This only works correctly if the first commit works after a retry, if
a latter commit has to be retried then it gets re-cherry-picked onto
the target branch rather than its own parent.

Fix by remembering the previously successful cherry-picked commit and
resetting to *that*. However I can't really test it because it's
rather hard to get into a situation where the rename detection fails
using synthetic tests.

While at it, clean the logs by stripping the "performing inexact
rename detection" stuff from all stderr (both the CherrypickError from
which it was already stripped and the debug messages).

Fixes #444
2021-01-11 14:43:36 +01:00
..
data [ADD] forwardport: policy on PR form 2020-07-14 13:34:05 +02:00
migrations/13.0.1.1 [IMP] forwardport: reliability of PR reminders 2020-05-26 15:56:36 +02:00
models [FIX] forwardport: broken fp if intermediate commit requires renamelimit=0 2021-01-11 14:43:36 +01:00
tests [CHG] runbot_merge, forwardport: remove labelling 2020-11-20 07:41:54 +01:00
__init__.py [ADD] forwardbot 2019-09-05 10:00:07 +02:00
__manifest__.py [IMP] forwardport: reliability of PR reminders 2020-05-26 15:56:36 +02:00