News for hackers. Stuff that matters.
Re:How Rust is tested by richdougherty on Monday July 10, 2017 @11:50PM (#14741454)
If cost is a factor then you could use batch testing as your default mode of operation and not bother testing individual commits at all unless a batch fails.

Using batch testing as a default would both reduce costs and increase merge speed, assuming that your commits usually pass testing.

The downside of using batching as a default is that it wouldn't test every commit in isolation. That means it wouldn't necessarily be safe to roll back to a particular commit if that commit was tested as part of a batch. E.g. if patches A, B and C were tested together, then it's not certain that patch A by itself would pass the tests.

Re:How Rust is tested by computerphage on Tuesday July 11, 2017 @12:02AM (#14741494)
That's a good point that I didn't consider. You could squash commits to get that property back, but the results wouldn't carry much meaning.