[mythtv-commits] Ticket #11224: Duplicate recordings without manual resched - 0.26 regression
MythTV
noreply at mythtv.org
Sun Nov 11 20:32:50 UTC 2012
#11224: Duplicate recordings without manual resched - 0.26 regression
--------------------------------------+----------------------------
Reporter: Bradley Baetz <bbaetz@…> | Owner: gigem
Type: Bug Report - General | Status: assigned
Priority: minor | Milestone: unknown
Component: MythTV - Scheduling | Version: 0.26-fixes
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
--------------------------------------+----------------------------
Comment (by gigem):
Okay, here's the smoking gun right where I expected it.
{{{
Nov 11 14:10:00 guava mythlogserver: mythbackend[30793]: I Scheduler
scheduler.cpp:2156 (HandleReschedule) Reschedule requested for CHECK -3
298 0 UpdateRecStatus2 | JAG | Baby, It's Cold Outside | Former fighter
pilot Captain Harmon 'Harm' Rabb and his team of lawyers are charged with
the duty of investigating and litigating crimes committed by marine and
navy personnel. |
Nov 11 14:10:00 guava mythlogserver: mythbackend[30793]: I Scheduler
scheduler.cpp:2231 (HandleReschedule) CreateTempTables...
Nov 11 14:10:00 guava mythlogserver: mythbackend[30793]: I Scheduler
scheduler.cpp:2237 (HandleReschedule) UpdateDuplicates...
Nov 11 14:10:00 guava mythlogserver: mythbackend[30793]: I Scheduler
scheduler.cpp:58 (DumpRecordMatch) Dumping recordmatch Before
UpdateDuplicates()
Nov 11 14:10:00 guava mythlogserver: mythbackend[30793]: I Scheduler
scheduler.cpp:80 (DumpRecordMatch) rid=298, chid=1011, st=Sun Nov 11
02:00:00 2012, mid=0, ord=0, rd=0, fd=0, ors=0, fid=0
Nov 11 14:10:00 guava mythlogserver: mythbackend[30793]: I Scheduler
scheduler.cpp:80 (DumpRecordMatch) rid=298, chid=1011, st=Sun Nov 11
14:00:00 2012, mid=0, ord=0, rd=0, fd=0, ors=0, fid=0
}}}
ord should be -1 for any programs matching the CHECK reschedule request,
but they are being left at 0. That causes them to not be considered for
the following duplicate update. So the question is why isn't ord being
set to -1. It's not obvious to me why this is happening. Perhaps there's
something unique in your guide data or configuration or the scheduler
logic is just faulty.
Can you please add "database" to your backend logging to see the actual
query being used? Then, try running the query manually in mysql and
perhaps see why it's not working as intended.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/11224#comment:5>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list