3 ms·
> I don't think it can be done 'as-you-type' due to resource constraints. But I do think it can be done pre-commit. When you rent a Google Compute Engine machi
by runeks 10y ago
> I don't think it can be done 'as-you-type' due to resource constraints. But I do think it can be done pre-commit.
When you rent a Google Compute Engine machine, it doesn't matter how much you use the CPU, the monthly cost is the same (roughly $30/vCPU/month). So you incur no additional cost by restarting tests after each input character. And if we can spread multiple users' tests out over multiple machine instances, the cost would remain constant per user, but their tests would execute in parallel on multiple instances.
- sytse 10y agoIf you restart the tests it indeed doesn't matters less. Currently GitLab doesn't allow for an easy cancel and rerun I think. Also keep in mind that that testing can keep over 30 CPU's busy for 5 minutes. I think it makes more sense to start that when a human indicates it. But we can also consider 'restart as you type' and 'restart when you save'. Thanks for your suggestion.