runbot/runbot_merge/controllers
Xavier Morel e309e1a3a2 [FIX] runbot_merge: don't over-bump timeout
By updating the staging timeout every time we run `_compute_state` and
still have a `pending` status, we'd actually bump the timeout *on
every success CI* except for the last one. Which was never the
intention and can add an hour or two to the mergebot-side timeout.

Instead, add an `updated_at` attribute to statuses (name taken from
the webhook payload even though we don't use that), read it when we
see `pending` required statuses, and update the staging timeout based
on that if necessary.

That way as long as we don't get *new* pending statuses, the timeout
doesn't get updated.

Fixes #952
2024-09-20 12:17:17 +02:00
..
__init__.py [FIX] runbot_merge: don't over-bump timeout 2024-09-20 12:17:17 +02:00
dashboard.py [FIX] runbot_merge: don't show details of merged PR on GH 2024-08-05 15:18:19 +02:00
reviewer_provisioning.py [FIX] runbot_merge: make provisioning more resilient 2023-06-21 14:26:19 +02:00