New files not analyzed - Needs update to compare with last run release opposed to latest file present in the log directory #10
Description
Very common scenario experienced during rescans (Due to source delivery issue or rescan failure and reruns etc.)
We have snapshot-1, unanalyzed report Path-1
Snapshot-2, unanalyzed report Path-2,
snapshot-3, unanalyzed report path-3.
When we restore to snapshot -1, the path of the unanalyzed log file in cms will be path-1.
Now if i do snapshot-4, it should use path-1 for comparison, as CMS will have that info stored. But instead what is currently happening is that it compares Path-3 (which is no longer valid file) with Path-4 and shares the results.
Discussed the scenario with Mathieu on 10/17.