From: Anthony PERARD <anthony@xenproject.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [XEN PATCH 6/9] CI: Upload junit result as artefact
Date: Tue, 3 Jun 2025 18:03:06 +0200 [thread overview]
Message-ID: <aD8cuiPrWjo_GGIK@l14> (raw)
In-Reply-To: <30007ef7-9576-41fb-8d4d-08ae7cbdacc4@citrix.com>
On Tue, Jun 03, 2025 at 02:13:59PM +0100, Andrew Cooper wrote:
> On 03/06/2025 1:42 pm, Anthony PERARD wrote:
> > From: Anthony PERARD <anthony.perard@vates.tech>
> >
> > This allow to investigate the file in cases of error. Not all
> > jobs that extend ".adl-x86-64" are creating a "tests-junit.xml" but
> > Gitlab only produce a warning when the file isn't found.
>
> I'm not sure what you're trying to say here.
I guess I can shorten the message to (with some rewording):
"This allows to investigate the junit file in cases of parse error."
I guess it doesn't matter if a gitlab job is expected to produce
"tests-junit.xml" or not.
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2025-06-03 16:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 12:42 [XEN PATCH 0/9] CI: Fixes for tools/tests and junit and other Anthony PERARD
2025-06-03 12:42 ` [XEN PATCH 1/9] CI: Add SELECTED_JOBS_ONLY to analyze.yaml Anthony PERARD
2025-06-03 13:09 ` Andrew Cooper
2025-06-03 18:21 ` Stefano Stabellini
2025-06-03 12:42 ` [XEN PATCH 2/9] tools/tests: Fix return value of test-rangeset Anthony PERARD
2025-06-03 13:07 ` Andrew Cooper
2025-06-03 12:42 ` [XEN PATCH 3/9] CI: Fix status check for tools/tests Anthony PERARD
2025-06-03 13:07 ` Andrew Cooper
2025-06-03 18:22 ` Stefano Stabellini
2025-06-03 12:42 ` [XEN PATCH 4/9] CI: Ignore run-tools-test return value Anthony PERARD
2025-06-03 13:26 ` Andrew Cooper
2025-06-03 13:41 ` Marek Marczykowski-Górecki
2025-06-03 12:42 ` [XEN PATCH 5/9] CI: Have the gitlab job fail on tools/tests failure Anthony PERARD
2025-06-03 13:41 ` Andrew Cooper
2025-06-03 13:44 ` Marek Marczykowski-Górecki
2025-06-03 14:09 ` Andrew Cooper
2025-06-03 14:26 ` Andrew Cooper
2025-06-03 15:58 ` Anthony PERARD
2025-06-03 17:13 ` Andrew Cooper
2025-06-03 12:42 ` [XEN PATCH 6/9] CI: Upload junit result as artefact Anthony PERARD
2025-06-03 13:13 ` Andrew Cooper
2025-06-03 16:03 ` Anthony PERARD [this message]
2025-06-03 12:42 ` [XEN PATCH 7/9] CI: Use CDATA avoid the need to escape tests outputs Anthony PERARD
2025-06-03 13:04 ` Andrew Cooper
2025-06-03 18:27 ` Stefano Stabellini
2025-06-03 12:42 ` [XEN PATCH 8/9] CI: Workaround extra content in junit Anthony PERARD
2025-06-03 14:12 ` Andrew Cooper
2025-06-03 16:23 ` Anthony PERARD
2025-06-03 18:29 ` Stefano Stabellini
2025-06-03 18:37 ` Marek Marczykowski-Górecki
2025-06-03 21:49 ` Stefano Stabellini
2025-06-03 12:42 ` [XEN PATCH 9/9] CI: Add timing to junit Anthony PERARD
2025-06-03 14:16 ` Andrew Cooper
2025-06-03 18:35 ` Stefano Stabellini
2025-06-04 8:48 ` Anthony PERARD
2025-06-04 10:57 ` Andrew Cooper
2025-06-04 11:33 ` Marek Marczykowski-Górecki
2025-06-04 20:17 ` 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=aD8cuiPrWjo_GGIK@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.