mirror of
https://github.com/odoo/runbot.git
synced 2025-03-17 00:15:47 +07:00
b45ecf08f9
Github can fail to create the magic refs on PRs (`pull/refs/?/head`). Since forwardport relies on these refs to fetch PR content this is an issue when it occurs, as the forward ports fail in a loop. After discussion with Github support, it turns out Github enabled `allowReachableSHA1InWant` a while back, meaning it's possible to fetch content by commit (rather than ref) as long as the content is "in network". Use this property as fallback when checking if we can see the PR head before forward porting. Also: - remove explicit configuration of GC during fetch, it doesn't disable the autogc (yet?) but that's likely going to happen anyway - update logging and logger hierarchy during forward port to make things clearer and easier to extract, although based on PR id rather than number - rate limit failing forward ports to avoid running them on every cron (~ every minute), run them every ~30mn instead, this provides higher odds of recovery with less log garbage in case of transient github failure, and if the PR is stuck it limits the log pollution Fixes #658 |
||
|---|---|---|
| .. | ||
| changelog | ||
| data | ||
| migrations/13.0.1.1 | ||
| models | ||
| tests | ||
| __init__.py | ||
| __manifest__.py | ||
| controllers.py | ||