Michael Mohr <[email protected]> writes: > Good morning; > > I'm attempting to implement a system level test framework using Avocado. At > the moment, I'm trying to determine whether it is possible to run multiple > instances of one or more test modules in parallel within the current Avocado > framework. A simple example would be running "dd" on a collection of drives > attached to an HBA. Certainly it is possible to just enumerate attached > drives using e.g. python-parted and loop over them all, starting > process.SubProcess instances on all of them. But this example is still too > simple; what if, for example, it is desirable to run fio or badblocks on some > of them instead? I'd prefer to implement separate test modules to support > different drive stressors so that the implementation of each stressor is > clean but the calling interface is unified. Further, what if it is desirable > to run multiple instances of one or more stressor test modules on a single > rotational drive (to force the drive heads to move around randomly)? > > The above just addresses drive stress. The CPUs and memory should be > stressed at the same time, and would require different test modules. If > there is any guidance on this usage of Avocado within the documentation, I've > not yet seen it. It is planned https://trello.com/c/xNeR2slj/255-support-running-tests-in-parallel but not implemented yet. IMHO everything is reado to that, but not implemented yer. As workaround you may wrap avocado with GNU/parallel [1] or Jenkins pipeline [2]
> > Michael Mohr > Office: 510-668-3527 > Mobile: 510-449-9331 > Hyve Solutions > [hyve-solutions] Footnotes: [1] https://www.gnu.org/software/parallel/ [2] https://www.cloudbees.com/blog/parallelism-and-distributed-builds-jenkins
signature.asc
Description: PGP signature
