On Sat, Apr 10, 2021 at 06:41:03AM +0200, Thomas Huth wrote: > On 09/04/2021 21.01, Stefan Hajnoczi wrote: > > It can be tricky to troubleshoot qos-test when a test won't execute. Add > > an explanation of how to trace qgraph node connectivity and find which > > node has the problem. > > > > Cc: Emanuele Giuseppe Esposito <eespo...@redhat.com> > > Cc: Paolo Bonzini <pbonz...@redhat.com> > > Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com> > > --- > > docs/devel/qgraph.rst | 58 +++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 58 insertions(+) > > > > diff --git a/docs/devel/qgraph.rst b/docs/devel/qgraph.rst > > index a9aff167ad..4635efb2c2 100644 > > --- a/docs/devel/qgraph.rst > > +++ b/docs/devel/qgraph.rst > > @@ -92,6 +92,64 @@ The basic framework steps are the following: > > Depending on the QEMU binary used, only some drivers/machines will be > > available and only test that are reached by them will be executed. > > +Troubleshooting unavailable tests > > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > +If there is no path from an available machine to a test then that test will > > +unavailable and cannot execute. This can happen if a test or driver did > > not set > > "will be unavailable" ? or "will be marked as unavailable" ? > > Apart from that, patch looks fine to me.
Thanks, will fix. Stefan
signature.asc
Description: PGP signature
