I was debugging this by printing out coverage reports etc, and noticing that the .coverage file genuinely thinks that there was 0% coverage, when we expect %100.