What steps will reproduce the problem?
1. cron launches the video processing task
2. the video is set as processing in the DB
3. some check/transcoding step goes wrong
What is the expected output? What do you see instead?
The video is kept as processing in the DB and thus is not eligible to process
the next time the cron task is launched.
If one of the steps didn't go as expected the entire process should be
rolled-back and thus the DB should change the video to 'Unprocessed'
Original issue reported on code.google.com by inkoperu...@gmail.com on 20 Apr 2011 at 4:02
Original issue reported on code.google.com by
inkoperu...@gmail.com
on 20 Apr 2011 at 4:02