1907116 - [meta] Improve end-to-end time for the code review bot

Status: NEW

(Developer Infrastructure :: Source Code Analysis, enhancement)

Description

[Marco Castelluccio [:marco]]

Taking https://phabricator.services.mozilla.com/D216152 (with linked try push https://treeherder.mozilla.org/jobs?repo=try&revision=8ecfe1dd921371b05eec3d240e5de989ec9e09ba) as an example:
revision opened 12:06
push 12:08
decision task requested 12:12
decision task started 12:12
decision task finished 12:17
doc task requested 12:17
doc task started 12:26
doc task finished 12:43
code-review-issues task finished 12:45
code review bot task triggered 13:49
issues published 13:49

Many of these steps can be optimized.

Comment 1

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

9 minutes waiting time for the doc task to get a machine. A look just now at the worker pool shows only one machine running but half an hour ago 10+ were busy. No base load of finishing machines means the task has to wait for a machine requested for it which first needs to finish its setup.