mirror of
https://github.com/odoo/runbot.git
synced 2025-03-18 00:45:49 +07:00
8a931adeac
When an fw batch fails, log a message to its chatter (so the reason for the failure doesn't necessarily have to be hunted down in the logs, although depending on the quality of the error that might still be an issue). Also if a batch keeps failing (fails for more than a day at a retry every hour -- increased from a previous 30mn), stop retrying it and flag it in the list view, it's clearly not going to go through. This is because we hit an issue with a completion fw batch created on January 27th which kept failing until it was deleted on February 10th. Thankfully it failed on `git push` and git operations apparently are not rate limited at all, but still it's not great stewartship to keep trying a forwardport which keeps failing. Retrying in case of transient failure makes sense, but after 24 attempts over a day it's either not transient, or it's not working because github is down and hammering it won't help. |
||
|---|---|---|
| .. | ||
| crons.xml | ||
| queues.xml | ||
| security.xml | ||
| views.xml | ||