Project

General

Profile

Feature #11657

report locked machines to consumers of run information

Added by Greg Farnum over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
05/15/2015
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:

Description

We're persistently seeing machines which are locked for old jobs by scheduled suite runs, or occasionally other things. These nodes are hard to identify: nothing in pulpito or the suite emails gives any indication that this is likely, and the only way to identify it is by listing the nodes and checking them. (I have a few console grep lines and things to make this easier, but it's tedious and has to be checked by a person whenever we feel like it.)

This seems like something a computer could do! Summary emails from a run could include a line at the top about how many machines are still locked to the run. Pulpito could check the lock states when it's generating information. Please implement at least one of these so we have a better chance of detecting and dealing with stale locks.

History

#1 Updated by Greg Farnum over 4 years ago

  • Assignee set to Zack Cerza

Please prioritize as appropriate, Zack. Note when doing so that I've been doing this in sepia a couple times a week and always unlock at least 5, sometimes 20 nodes. That's a pretty big fraction of our testing capacity.

Also available in: Atom PDF