qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH v2 0/2] docs/devel/qgraph: add troubleshooting information
Date: Tue, 13 Apr 2021 09:34:24 +0200	[thread overview]
Message-ID: <6c4a9afa-55aa-4778-fa62-a49cbc55be28@redhat.com> (raw)
In-Reply-To: <20210412143437.727560-1-stefanha@redhat.com>

On 12/04/21 16:34, Stefan Hajnoczi wrote:
> v2:
>   * Fix "will unavailable" typo [Thomas]
> 
> I recently needed to troubleshoot a case where qos-test terminated immediately
> with no output. In other words, qos-test decided that no tests are runnable.
> 
> After lots of head scratching and some help from Emanuele it turned out that
> the machine types weren't being detected as expected.
> 
> These patches add documentation about how to troubleshoot similar cases in the
> future.
> 
> Stefan Hajnoczi (2):
>    libqos/qgraph: fix "UNAVAILBLE" typo
>    docs/devel/qgraph: add troubleshooting information
> 
>   docs/devel/qgraph.rst       | 58 +++++++++++++++++++++++++++++++++++++
>   tests/qtest/libqos/qgraph.c |  2 +-
>   2 files changed, 59 insertions(+), 1 deletion(-)
> 

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks, this is helpful.

Paolo



      parent reply	other threads:[~2021-04-13  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 14:34 [PATCH v2 0/2] docs/devel/qgraph: add troubleshooting information Stefan Hajnoczi
2021-04-12 14:34 ` [PATCH v2 1/2] libqos/qgraph: fix "UNAVAILBLE" typo Stefan Hajnoczi
2021-04-12 14:34 ` [PATCH v2 2/2] docs/devel/qgraph: add troubleshooting information Stefan Hajnoczi
2021-04-13  7:34 ` Paolo Bonzini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6c4a9afa-55aa-4778-fa62-a49cbc55be28@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).