When running processCcd.py on multiple visits, self-contradictory outputs are generated by the logger. For example:
The problem above is that the visit numbers don't match, but there should be no way for this to ever be the case, as far as I can see. FWIW, the second number is the true visit number, at least in my case.
This is only noticeable when --longlog is used, to allow disentangling of parallel processed data, but I don't know whether that means the logger is also wrong when sequentially running multiple visits on a single core (I suspect it's OK in that instance, but I'm not certain).
This bug is bad for tracking down which visits are failing and why.