28.07.2021, 23:10
Bit of a weird one:
I set up an encode batch and noticed that after one of the jobs supposedly finished that the batch didn't continue despite a long queue of "waiting", took a closer look at the sub jobs and noticed that it had finished up to before muxing with everything after showing as waiting, then noticed that there were 100 sub jobs listed! (with the 100th listed after the 10th?)
Manually ran the next job in the queue and it completed fine.
I then looked through the rest of the queue and found another job with over 100 sub jobs, ran it, it also stopped at muxing.
Next I started from scratch again and re-input the first failed file to see if I could recreate it.
This time the sub jobs listed in natural order but again it stopped at muxing
Oddly the 100th file completed by itself? (I'm guessing there some sort of flag after the "final" font deletion that signals job complete?)
And here's the debug of the retry:[attachment=1468]
Kinda curious why.
My initial guess was mkvmerge was silently failing due to an excessive number of attachments or parameters but the retry still triggering sub job 100 made me second guess myself and suggest that the script/parser has an issue with triple digit numbers of sub jobs?
I set up an encode batch and noticed that after one of the jobs supposedly finished that the batch didn't continue despite a long queue of "waiting", took a closer look at the sub jobs and noticed that it had finished up to before muxing with everything after showing as waiting, then noticed that there were 100 sub jobs listed! (with the 100th listed after the 10th?)
Manually ran the next job in the queue and it completed fine.
I then looked through the rest of the queue and found another job with over 100 sub jobs, ran it, it also stopped at muxing.
Next I started from scratch again and re-input the first failed file to see if I could recreate it.
This time the sub jobs listed in natural order but again it stopped at muxing
Oddly the 100th file completed by itself? (I'm guessing there some sort of flag after the "final" font deletion that signals job complete?)
And here's the debug of the retry:[attachment=1468]
Kinda curious why.
My initial guess was mkvmerge was silently failing due to an excessive number of attachments or parameters but the retry still triggering sub job 100 made me second guess myself and suggest that the script/parser has an issue with triple digit numbers of sub jobs?