Hi, > I also think that approach #1 is simpler and saner, but thinking about > where we're going with the test runner development, I started to have > doubts about it. The reason is that we're adding parallel and multi > environment (process, machine, container) execution capabilities to the > runner. Dogfood version is here: > > https://github.com/avocado-framework/avocado/pull/3111 > > By doing all download/caching before any single test starts, we may be > wasting a lot of CPU time that could be used for running tests, making > the overall job execution much longer.
Well, if the internet link is the bottleneck running downloads in parallel wouldn't speed up things ... Also given that avocado caches the downloads the common case will probably be to not download anything. > FIY: one of the new runner planned features, is based on a question > use case you mention, about how to run tests built into a minimal > image, such as an initrd. FYI: Here is what I did: https://git.kraxel.org/cgit/drminfo/tree/tests cheers, Gerd
