TimerSanityCheck can report a failure when it should be OK

[birdman]

I'm having problems with getting a recording to be enabled.

There are two existing timers:

20:57 to 22:45
20:57 to 22:05

The one I'm trying to add is for:

22:27 to 23:20

i.e. after the latter of those first two timers has finished I should have a free tuner for that next recording to run; but TimerSanityCheck reports otherwise.

I've added some debug statements to TimerSanityCheck.py to see what is going on. All I can see is that
the fakeRecService.start(True) produces an abnormal result (True not False?), so then

if not fakeRecResult: # tune okay

fails. The code then goes on to add an item of "DVB-T" to tunerType. This still leaves it as a failure, though.
I haven't (yet?) been able to find what handles that fakeRecService.start(True) call. (EDIT: eDVBServiceRecord::start() in lib/service/servicedvbrecord.cpp?)

The odd thing is that if I edit the start time of one of those timers to be 20:55 then the sanity check passes OK (so is it cause by having timers starting up at the same time?). However, since these are set by autotimers, when that runs again it resets the start times and then on the following autotimer scan it throws up the clash again.