runbot/forwardport
Xavier Morel 0b1e33da7c [IMP] forwardport: mitigate cat-file not finding commit on updates
Fix #457 hopefully: I didn't manage to repro / create a test for.

It looks like in some cases during the update process the PR ref lags
behind the branch itself. This means `forwardport.updates` creates a
new commit, pushes it, then on the next iteration updates the local
cache, tries to find the commit we just pushed... and that fails.

I can only assume this is because when there's enough load on the
github side the update to the `info/refs` pseudo-file can fall
behind (it's now 4MB and holding nearly 65k refs).

So cheat: take the commit we just pushed to the dev remote
and... immediately push it to the local cache under a dummy branch,
which we delete. Since we only gc "1 day ago" this should not vacuum.
2021-03-02 14:28:32 +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 [IMP] forwardport: mitigate cat-file not finding commit on updates 2021-03-02 14:28:32 +01:00
tests [FIX] forwardport: duplicates forwardport on edition 2021-03-02 14:28:32 +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