Phabricator source code analysis takes a long time to run (> 1 day)
Categories
(Developer Infrastructure :: Source Code Analysis, defect, P2)
Tracking
(Not tracked)
People
(Reporter: mcomella, Unassigned)
Details
I'm working on a changeset in phabricator: https://phabricator.services.mozilla.com/D143858
The Source Code Analysis (via reviewbot) took 1d, 19 hours to run: https://phabricator.services.mozilla.com/harbormaster/build/513785/ That seems extreme, especially considering the actual task treeherder -> phabricator task seemed to take ~28 minutes.
Timeline of events:
- Wed, Apr 27 10:44: I updated to new revision
- Wed, Apr 27 10:44: Harbormaster completed remote builds (this timestamp actually seems to indicate when it starts an HTTP request, not when it completes the builds)
- Fri, Apr 29, 06:08:02: Gecko decision task on treeherder receives the push
- Fri, Apr 29, 06:25 reviewbot comments on revision
- Fri, Apr 29, 06:36: Buildable completes
It seems the delay may be caused by the initial request to treeherder from phabricator.
I've since made additional changes to the changeset, which created a new static analysis request/buildable: https://phabricator.services.mozilla.com/B419201 It says:
Build 514797 Source Code Analysis
Target 693187 Make HTTP Request
where "Make HTTP Request" is grayed out. I don't know what HTTP Request it's making but maybe that's the cause.
|
||
Comment 1•3 years ago
|
||
Andi, this was due to some slowdown while pushing to try, right?
|
||
Comment 2•3 years ago
|
||
Yes, try was extremely slow for a while, so the queue that we consume got bigger and bigger.
|
||
Comment 3•3 years ago
|
||
The severity field is not set for this bug.
:andi, could you have a look please?
For more information, please visit auto_nag documentation.
|
|
||
Updated•3 years ago
|
|
||
Updated•3 years ago
|
Description
•