News for hackers. Stuff that matters.
Re:Where do Google's flaky tests come from? by sebcat on Saturday February 02, 2019 @04:43AM (#19062109)
When doing anything concurrently and/or in parallel, it is always good to have an input queue and an upper bound on the number of tasks (/threads/processes/...). Also an asynchronous flow.

You need to handle other problems (back-pressure, priorities, timeouts, ...) but if you need it you need it.

Re:Where do Google's flaky tests come from? by zenexer on Saturday February 02, 2019 @06:15AM (#19062443)
But how do you go about creating tests for all of that?
Re:Where do Google's flaky tests come from? by cyphar on Saturday February 02, 2019 @08:22AM (#19062848)
You don't need to write your own and test it -- use something like GNU parallel (if your tests can be run individually as commands or shell scripts) or a test framework that supports parallelism.