so anything that changes a test or what it is testing has to pass N times in a row in that job to merge, but tests that haven't changed get to use their cached results? I like the theory. I wonder if things low in the dependency tree would blow out the test time.