From: Anthony PERARD <anthony@xenproject.org>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [XEN PATCH v2 3/3] CI: Workaround extra content in junit
Date: Wed, 13 Aug 2025 14:46:25 +0200 [thread overview]
Message-ID: <aJyJIYKioCoVn4SP@l14> (raw)
In-Reply-To: <aJd2eHFgiLBNiWCy@mail-itl>
On Sat, Aug 09, 2025 at 06:25:28PM +0200, Marek Marczykowski-Górecki wrote:
> On Wed, Jul 30, 2025 at 05:26:02PM +0200, Anthony PERARD wrote:
> > From: Anthony PERARD <anthony.perard@vates.tech>
> >
> > Signed-off-by: Anthony PERARD <anthony.perard@vates.tech>
>
> Is it still an issue? AFAIR similar issue was fixed together with fixing
> xml upload hanging.
It was an issue in June:
https://lore.kernel.org/xen-devel/20250603124222.52057-9-anthony@xenproject.org/
And it still is:
https://gitlab.com/xen-project/people/marmarek/xen/-/jobs/10969191455
> WARNING: Found 75 too many lines in junit.
Thanks,
--
Anthony PERARD
prev parent reply other threads:[~2025-08-13 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 15:25 [XEN PATCH v2 0/3] CI: Fixes for tools/tests and junit and other Anthony PERARD
2025-07-30 15:26 ` [XEN PATCH v2 1/3] CI: Rework run-tools-test exit path Anthony PERARD
2025-08-09 16:22 ` Marek Marczykowski-Górecki
2025-08-13 12:38 ` Anthony PERARD
2025-07-30 15:26 ` [XEN PATCH v2 2/3] CI: Upload junit result as artefact Anthony PERARD
2025-08-09 16:23 ` Marek Marczykowski-Górecki
2025-07-30 15:26 ` [XEN PATCH v2 3/3] CI: Workaround extra content in junit Anthony PERARD
2025-08-09 16:25 ` Marek Marczykowski-Górecki
2025-08-13 12:46 ` Anthony PERARD [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=aJyJIYKioCoVn4SP@l14 \
--to=anthony@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=cardoe@cardoe.com \
--cc=marmarek@invisiblethingslab.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.