From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
andrew.cooper3@citrix.com, committers@xenproject.org,
michal.orzel@amd.com, xen-devel@lists.xenproject.org
Subject: Re: xen | Failed pipeline for staging | 6a47ba2f
Date: Tue, 2 May 2023 12:10:48 +0100 [thread overview]
Message-ID: <6450efbb.7b0a0220.9c334.a329@mx.google.com> (raw)
In-Reply-To: <333df991-58a8-f4e0-b46c-9f480cd34213@suse.com>
On Tue, May 02, 2023 at 08:53:31AM +0200, Jan Beulich wrote:
> I'm also having a hard time seeing what failure case the test ended
> up encountering: There are only two errors which can occur - one
> from the XSM hook (which is mishandled, and I'll make a separate
> patch for that) and the other from failing to copy back the info for
> the domain being looked at. I hope we can exclude the former, so are
> you suggesting the info struct copy-back is failing in your case?
Something's off somewhere, that's for sure. I'll post the remainder of
the series (not all of it made it to staging) so it's not left hanging
and start investigating this failure.
Cheers,
Alejandro
next prev parent reply other threads:[~2023-05-02 11:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <644bfbc6939d8_2a49bbb403253f4@gitlab-sidekiq-catchall-v2-78885c497-qxnp2.mail>
2023-04-29 3:05 ` xen | Failed pipeline for staging | 6a47ba2f Stefano Stabellini
2023-04-29 11:41 ` andrew.cooper3
2023-04-29 13:34 ` Marek Marczykowski-Górecki
2023-04-29 19:48 ` andrew.cooper3
2023-04-30 1:21 ` Stefano Stabellini
2023-05-02 3:59 ` Stefano Stabellini
2023-05-02 6:53 ` Jan Beulich
2023-05-02 11:10 ` Alejandro Vallejo [this message]
2023-05-03 14:38 ` dom0less vs xenstored setup race Was: " andrew.cooper3
2023-05-03 15:15 ` Julien Grall
2023-05-03 15:22 ` Juergen Gross
2023-05-03 15:33 ` andrew.cooper3
2023-05-03 21:53 ` Stefano Stabellini
2023-05-03 22:20 ` andrew.cooper3
2023-05-03 23:16 ` Stefano Stabellini
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=6450efbb.7b0a0220.9c334.a329@mx.google.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=committers@xenproject.org \
--cc=jbeulich@suse.com \
--cc=michal.orzel@amd.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.