Closed nvzard closed 6 years ago
Because IGitt is making more that one requests while calling write_repositories
method with an invalid token. That is sometimes taking more than 5secs and so the bot message queue is showing a queue.Empty
exception as the response is delayed due to IGitt's requests.
I restated the CI 5 times back to back and did not face any breakdown after increasing the timeout limit.
fwiw, if this unbreaks the tree, I think it is an acceptable workaround if an issue is raised in IGitt
so that followup work is done to prevent it biting us again.
Hey @nvzard, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
IGitt is doing its work as it is supposed to but it is making a second trial request because the token is invalid. This portion is handled by backoff https://pypi.org/project/backoff/ which makes the request function retry until some condition is met.
@nvzard , IGitt is causing this failure. If you cant disable the 'feature' of IGitt
causing this failure, then that is a problem in IGitt
. And please remove 'fix' from this commit message. It hasnt fixed anything. It has only obscured the problem, and it will bite us again another day. This is a workaround at best. :P A very useful workaround to get the builds working again, but we still need a solution to the problem.
50 char limit on commit shortlog.
@gitmate-bot ff
Hey! I'm GitMate.io! This pull request is being fastforwarded automatically. Please DO NOT push while fastforward is in progress or your changes would be lost permanently :warning:
Automated fastforward with GitMate.io was successful! :tada:
Default 5 sec timeout was causing unexpected random CI failure.
Closes https://github.com/coala/corobo/issues/564
Reviewers Checklist
botcmd
andre_botcmd
decorators.