Is there any way to do this without the literal sleeps? Gitlab CI in particular appears to be very contended (I guess it runs in parallel on huge systems with vast numbers of unrelated containers). I've seen threads being created that are so starved they never run at all even in tests running for many tens of seconds.
I'm thinking some kind of custom plugin which orders operations using its own clock that it is incremented as certain requests arrive, but I don't have a fully-formed idea of how it would work. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW _______________________________________________ Libguestfs mailing list Libguestfs@redhat.com https://listman.redhat.com/mailman/listinfo/libguestfs