I've debugged this before, and it might be a problem specific to our repo. That's what I found when I wrote

--reporting-invalidation-report