From: Jason Andryuk <jason.andryuk@amd.com>
To: <dmukhin@ford.com>, <xen-devel@lists.xenproject.org>
Cc: <andrew.cooper3@citrix.com>, <anthony.perard@vates.tech>,
<jbeulich@suse.com>, <julien@xen.org>, <michal.orzel@amd.com>,
<roger.pau@citrix.com>, <sstabellini@kernel.org>
Subject: Re: [PATCH v5 6/6] automation: enable Argo debugging in CI
Date: Thu, 4 Jun 2026 14:53:44 -0400 [thread overview]
Message-ID: <df57d291-eaee-4d87-a8a5-a27766a096b8@amd.com> (raw)
In-Reply-To: <20260603194131.1468654-7-dmukhin@ford.com>
On 2026-06-03 15:41, dmukhin@ford.com wrote:
> Enable extra Argo traces in CI to help analyze any potential Argo issues.
>
> That covers eclair-*-allcode and alpine-3.18-gcc-debug jobs.
>
> Signed-off-by: Denis Mukhin <dmukhin@ford.com>
Reviewed-by: Jason Andryuk <jason.andryuk@amd.com>
next prev parent reply other threads:[~2026-06-04 18:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 19:41 [PATCH v5 0/6] argo: few log fixes dmukhin
2026-06-03 19:41 ` [PATCH v5 1/6] argo: lower level of noisy connection-refused log dmukhin
2026-06-03 19:41 ` [PATCH v5 2/6] argo: correct logline in ring_unmap() dmukhin
2026-06-03 19:41 ` [PATCH v5 3/6] argo: drop argo prefix from argo_dprintk() calls dmukhin
2026-06-03 19:41 ` [PATCH v5 4/6] argo: fixup argo_dprintk() dmukhin
2026-06-04 18:51 ` Jason Andryuk
2026-06-04 21:47 ` dmukhin
2026-06-03 19:41 ` [PATCH v5 5/6] argo: introduce CONFIG_ARGO_DEBUG dmukhin
2026-06-04 17:37 ` Jan Beulich
2026-06-04 18:52 ` Jason Andryuk
2026-06-04 21:47 ` dmukhin
2026-06-04 21:46 ` dmukhin
2026-06-03 19:41 ` [PATCH v5 6/6] automation: enable Argo debugging in CI dmukhin
2026-06-04 18:53 ` Jason Andryuk [this message]
2026-06-04 9:51 ` [PATCH v5 0/6] argo: few log fixes Oleksii Kurochko
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=df57d291-eaee-4d87-a8a5-a27766a096b8@amd.com \
--to=jason.andryuk@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmukhin@ford.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.