Yes, you are right. That's a major bug. To be honest: this code never run on VMs which don't support CPU-time. I was not able to find such VMs and too lazy to mock the cpu-time feature. My idea was to skip test execution completely if cpu-time info is not available. I'll add this