CIDuty/How To/High Pending Counts: Difference between revisions

CIDuty/How To/High Pending Counts (view source)

8 bytes added , 10 September 2015

Confirmed users

1,989

edits

@@ Line 34: / Line 34: @@
 There is no designated tool for finding these types of abuses. When looking for abuse, I check which branch the pending jobs are coming (usually try), and then walk back through the [https://treeherder.mozilla.org/#/jobs?repo=try treeherder] history for that branch looking for revisions with multiple jobs triggered.
-=== Are infrastructure problems are causing retries? ===
+=== Are infrastructure problems causing retries? ===
-The builds cannot fetch a package and retries. Retries spike load. Pending counts rise.
+For example, if the builds cannot fetch a package they will retry. Or if builds cannot upload their resulting binaries. For example, IT once implemented a DNS redirect to a server where we didn't have ssh keys to upload the resulting binaries. See: {{bug|1198296}} In this case builds fail, they retry and pending counts rise.
-The builds cannot upload their resulting binaries. This happened once when IT made DNS redirect to a server where we didn't have ssh keys to upload the resulting binaries. For example: {{bug|1198296}} In this case builds fail.
 === Is coalescing working? ===