We noticed that sometimes jobs get reloaded with a :
2016-09-10 13:26:40: 0: Plugin will be reloaded: Auxiliary files for the current job have been modified.
log line as the reason. But looking at the aux files, they havent changed at all. The job was submitted at 1.23pm, and all the aux files have that date. There is another file in the aux folder (an internal log), which is not listed as an aux file, not sure if changes to that file matter… (dont think it does, otherwise we would see restarts every frame…)
Would it be possible to figure out why deadline thinks an aux file has changed? Which file and what change did it detect? Also, can this misfire?
Looks like there is some weirdness going on with the logic used to determine if the auxiliary files have changed, we’ll look into it on our end. Thanks for reporting this!
Can you confirm that the job, who’s auxiliary files are coming up as out of sync, does not have the “Re-synchronize Auxiliary Files Between Tasks” flag set?
I looked through recent change logs, but couldn’t find anything related to this. Did you guys get around to looking into the logic here, or add additional logging to figure out what might cause the false positives?
Yeah, those changes are actually in 8.1 Beta 6. There were definitely a couple odd flows that caused unnecessary reloads, and it should now print out the individual aux files that caused the re-sync in the event that it is deemed necessary:
They won’t, unfortunately. We did some significant refactoring of the auxiliary file system in 8.1, and this change was part of that overall effort. We wouldn’t be able to backport this change without doing a similar amount of refactoring, and that’s too big of a change for an 8.0 revision release.
