-
Guillaume Tucker authored
In some cases, a device can be in the "running" state but still not have any current job associated with it. This causes some exceptions, as the code tries to get a `.pk` attribute from a None object. The root cause of the problem is likely due to some glitch in the state machine, where the device state changes before the new job has been associated with it. Work around this by printing a message with "(no current job)" when this happens, to avoid an exception and to help debug the root cause of the problem. Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
c2b3619d